-
Notifications
You must be signed in to change notification settings - Fork 3
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
Detect failing nix builds on CI #120
Conversation
This is ready for review. @maartenberg, can you please take a look? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes LGTM! I have one optional suggestion, feel free to merge either way.
# Print working directory for debugging purposes | ||
- "pwd" | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this still necessary?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not strictly, but I think it is useful to record the working directory since we are creating the nix-store-location
file there.
@OpsBotPrime merge on friday 😈 afternoon 👹 |
Pull request approved for merge by @rudymatela, rebasing now. |
Approved-by: rudymatela Auto-deploy: false
Rebased as b0bf0a6, waiting for CI … |
closes #119
This separates the
nix-build
andcachix store
steps of the build in two commands.Previously failures in
nix-build
were not being detected due to it not being the last command in the pipe. This PR fixes the issue by avoiding piping the two commands.