mozilla-services / mozilla-services/updatebot
If revision N fails to build, maybe we shouldn't try N+1?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 9
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
If a revision of a library causes a build failure, it's unlikely (but possible?) that a subsequent version of the library is going to fix that build failure. Perhaps instead of even trying N+1, we should switch to something better. Like waiting a certain amount of time before trying a new revision, or not doing any new revisions at all.
(Child of #83)
Contributor guide
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
No file, test, or entry point is named. Start by tracing how updatebot handles a failed revision build and determine whether it should wait, stop, or select another revision. Done means an explicit policy for subsequent revisions, with its behavior verified by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devops, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100