expose .drv of each build
Nobody has claimed this yet.
- Dominant language
- PLpgSQL
- Stars
- 1.6k
- Forks
- 358
- Avg merge
- 20h 30m
- Merged PRs (30d)
- 27
Description
Is your feature request related to a problem? Please describe.
There have been cases where Hydra's .drv differed from what was reproduced locally, and we couldn't find why. The outPath didn't differ, so there was not that much incentive to investigate further. However, if someone would like to dig into this further, it would be helpful to provide access to the contents of the .drv on Hydra.
Describe the solution you'd like
On the 'Details' tab of a build, the 'Derivation store path' should be a link, and clicking that link should download the .drv
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
Start at the build's Details tab and trace how the “Derivation store path” is rendered and how existing build files are exposed for download. Verify which .drv belongs to the build, then confirm that the path is a link and that clicking it downloads the .drv contents.
Written by the indexing model from the issue text.
Assessment
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100