Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: NixOS/nix
base: f961c07ca82c
Choose a base ref
...
head repository: NixOS/nix
compare: a85bbcc2f4b1
Choose a head ref
  • 8 commits
  • 15 files changed
  • 1 contributor

Commits on Jan 27, 2021

  1. Make the build-hook work with ca derivations

    - Pass it the name of the outputs rather than their output paths (as
      these don't exist for ca derivations)
    - Get the built output paths from the remote builder
    - Register the new received realisations
    thufschmitt committed Jan 27, 2021
    Copy the full SHA
    21b8c28 View commit details
    Browse the repository at this point in the history
  2. LocalStore: Send back the new realisations

    To allow it to build ca derivations remotely
    thufschmitt committed Jan 27, 2021
    Copy the full SHA
    5c44dae View commit details
    Browse the repository at this point in the history
  3. LegacySSHStore: Send back the new realisations

    To allow it to build ca derivations remotely
    thufschmitt committed Jan 27, 2021
    Copy the full SHA
    c700c93 View commit details
    Browse the repository at this point in the history
  4. RemoteStore: Send back the new realisations

    To allow it to build ca derivations remotely
    thufschmitt committed Jan 27, 2021
    Copy the full SHA
    f7d722b View commit details
    Browse the repository at this point in the history
  5. Also send ca outputs to the build hook

    Otherwise they don't get registered, triggering an assertion failure
    at some point later
    thufschmitt committed Jan 27, 2021
    Copy the full SHA
    8e94058 View commit details
    Browse the repository at this point in the history
  6. build-remote: Always register the missing outputs

    It's possible that all the paths are already there, but just not
    associated to the current drv output
    thufschmitt committed Jan 27, 2021
    Copy the full SHA
    1b469c8 View commit details
    Browse the repository at this point in the history
  7. Properly bypass the registering step when all outputs are present

    There was already some logic for that, but it didn't handle the case of
    content-addressed outputs, so extend it a bit for that
    thufschmitt committed Jan 27, 2021
    Copy the full SHA
    76de5a8 View commit details
    Browse the repository at this point in the history
  8. Copy the full SHA
    a85bbcc View commit details
    Browse the repository at this point in the history