Hydra does not make derivations available in the channel when $out is a symlink
Open
Nobody has claimed this yet.
- Dominant language
- PLpgSQL
- Stars
- 1.6k
- Forks
- 358
- Avg merge
- 20h 30m
- Merged PRs (30d)
- 27
Description
Example:
mkLink = name: target: pkgs.runCommand name { inherit target; } "ln -s $target $out";
mkLink2 = name: target: pkgs.runCommand name { inherit target; } "mkdir $out; ln -s $target $out/$name";
Jobs that are produced with mkLink do not end up in the channel, while those produced by mkLink2 do. An easy way to test this seems to be: checking for the presence of a 'one-click install' or 'nix closure' link on the build summary page.
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 with the mkLink and mkLink2 examples in the issue and reproduce the difference in Hydra's build summary page. Check whether the one-click install or Nix closure link appears for the symlinked $out case; done means those derivations are available in the channel like the directory case.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system, ci-cd
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100