Builds being deleted immediately
Nobody has claimed this yet.
- Dominant language
- PLpgSQL
- Stars
- 1.6k
- Forks
- 358
- Avg merge
- 20h 30m
- Merged PRs (30d)
- 27
Description
Hi,
It seems that builds vanish immediately after they finish. Eg at time of writing,
http://hydra.nixos.org/build/51448202
is only 30 minutes old, but already it says "Note: this build is no longer available.". Clicking the "Actions: contents" button results in a 404. This is especially problematic with failed builds when you want to investigate in more detail why they failed, eg
http://hydra.nixos.org/build/51447018
The "Failed build produced output. Click here to inspect the output" and closure referred to in the "Actions: help" link seem to go 404 right after the job ends.
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 by reproducing the behavior using builds 51448202 and 51447018, checking the build page, “Actions: contents,” failed-build output, and the closure after completion. Done means completed builds and failed-build outputs remain available for investigation instead of returning a 404.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system, ci-cd
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100