mozilla-releng / mozilla-releng/scriptworker-scripts
get rid of branches that deploy to multiple scriptworkers
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 16
- Forks
- 38
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 14
Description
We have production (and I think dev) that deploy to all the scriptworkers. IMO these are a big footgun because it makes it difficult to know what exactly is deployed somewhere. On multiple occasions I have accidentally reverted something because it was deployed through, eg: production instead of production-balrogscript.
@escapewindow - curious your thoughts here.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Inspect the deployment configuration and branch mappings for production, dev, production-balrogscript, and the scriptworkers. Confirm the intended one-branch-to-one-worker policy with maintainers; the work is done when multi-worker deployment branches are removed and each remaining mapping is unambiguous.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devops, release
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100