mozilla-releng / mozilla-releng/scriptworker-scripts
[meta] mitigate scriptworker rollout bustage
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 16
- Forks
- 38
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 14
Description
Recently, we rolled out an entire set of new k8s scriptworker pools via a push to the production branch, and a) the signingscript pool was busted because it was claiming tasks but had an incompatible version of osslsigncode due to a moved python:3.8 docker hub tag, and b) the rest of the pools were busted because they were using a version of scriptworker that didn't successfully claimWork.
On top of this, we didn't have an established, documented way of rolling back k8s pools; each person had their own way of doing so, or none at all. So:
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
Start with the four linked issues: scriptworker integration tests in CI, Dockerfile base-image digest pinning, signingscript integration tests, and documented Kubernetes pool rollback. Review each issue to determine its separate scope; this meta issue is done when all four follow-up items are completed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, kubernetes, python
- Domain
- ci-cd, devops, documentation, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100