Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hydra version is 8 months old. #44044

Closed
ElvishJerricco opened this issue Jul 24, 2018 · 3 comments · Fixed by #44841
Closed

Hydra version is 8 months old. #44044

ElvishJerricco opened this issue Jul 24, 2018 · 3 comments · Fixed by #44841
Labels
6.topic: nixos Issues or PRs affecting NixOS modules, or package usability issues specific to NixOS

Comments

@ElvishJerricco
Copy link
Contributor

The version of Hydra tracked in nixpkgs is 8 months behind Hydra master. Considering Hydra doesn't have a discrete release model, it seems nixpkgs ought to be rolling with master at least somewhat promptly. Is there a reason that it is so out of date, or does someone just need to send a PR bumping it?

@FRidh
Copy link
Member

FRidh commented Jul 24, 2018

Does the NixOS module work? In any case, yes, just send a PR. Do make sure you've tested it.

@FRidh FRidh added the 6.topic: nixos Issues or PRs affecting NixOS modules, or package usability issues specific to NixOS label Jul 24, 2018
@Ma27
Copy link
Member

Ma27 commented Jul 29, 2018

@FRidh I have a private Hydra and the module seems to work fine. However I’d be interested in an upgrade (and a release model 😅), so I’d give a bump a try next week:)

@Ma27
Copy link
Member

Ma27 commented Aug 9, 2018

FYI I just started working on the bump, I'll try keep this thread update :)

Ma27 added a commit to Ma27/nixpkgs that referenced this issue Aug 13, 2018
This bumps Hydra to the latest revision available. As Hydra doesn't have
a release model (and therefore no tags) ATM, the derivation will pin
against the actual git revision and the date of the commit in the
derivation name.

Additionally the following changes have been made:

* Dropped `postUnpack` phase. It is useful when working with the Hydra
  source (and no dirty changes shall be used in `release.nix`, but is has
  no use in `nixpkgs`).

* Added myself as maintainer to have more folks available in case of
  future breakage.

* Implemented support for Nix 2.0 and `unstable` (currently 2.1):

  Since 1672bcd in NixOS/nix the
  evaluator differentiates between `settings` and `evalSettings`.
  Previously `restrictEval` in `hydra-eval-jobs.cc` has been set in
  `settings`, this doesn't work anymore in Nix 2.1 and is therefore
  incompatible to Nix 2.0 on an API level.

  To resolve this, the flag `isGreaterNix20` parses the version string
  of `pkgs.nix` and applies a patch if nix.version<=2.0.

  Furthermore the Hydra build with Nix 2.1 requires `boost` as build input
  which is not needed for Nix 2.0. To avoid unnecessary increase in the
  closure size this library will only used as build input for
  nix.version>2.0.

* Fixed the NixOS test for `hydra`:
  disabled binary cache to allow sandbox builds (otherwise it would
  query `cache.nixos.org` during the Hydra build inside the test).

  Additionally the trivial.nix jobset required simplification (as done
  in NixOS/hydra, e.g. tests/api-test.nix) as bash is not available in
  the build sandbox as builder (even when adding pkgs.bash to
  systemPackages).

  The easiest workaround to confirm a the functionality of a jobset
  without importing nixpkgs is to use the default shell /bin/sh which
  is mounted from `pkgs.busybox` into the build env
  (NixOS#44841 (comment)) in the
  VM and a named pipe to create $out.

Closes NixOS#44044
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
6.topic: nixos Issues or PRs affecting NixOS modules, or package usability issues specific to NixOS
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants