Allow to specify the base revision for PR build
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 323
- Forks
- 171
- PR merge metrics
- No merged PRs in 30d
Description
Sometimes the dependencies of a pull request cannot be built for unrelated reasons, but it is very unlikely that the specific way of fixing them will matter for the PR in question. In other cases the dependencies are not even broken, but the current revision in the base branch hasn't been built far enough on Hydra.
In such a case it would be convenient to build the PR on top of a different base revision. Ideally it would be the latest revision that has a specified set of packages available in the Hydra cache, but manual specification of revision would already be very useful.
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 by tracing how ofborg builds pull requests against the base branch and how Hydra cache availability is checked. Define how a manually supplied base revision and a revision selected from available packages should be represented; done means a PR can build on the selected revision when its normal base is unsuitable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system, ci-cd, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100