-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Update nix dev env, add CI jobs to facilitate maintenance #10316
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
base: master
Are you sure you want to change the base?
Conversation
I would like to use the dev env provided by nix to build foundry but it's quite outdated. This PR makes it up to date and automated some of the maintenance. Use solc from nixpkgs instead of custom flake. This will at least update solc when it's updated in nixpkgs versus remaining on the same version until someone manually edits flake.nix and makes a PR. Add a CI job to ensure the nix dev env can be used to build foundry. I would like to make it possible to run all the tests too but this would requires more work to track down reasons for the invididual test failures.
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.
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.
Nice, thanks for the update and CI job!
I think it would be good to set up a CI for it before making the flake more complex. That's also suggested in comments on #9260. |
Motivation
I would like to use the dev env provided by nix to build foundry but it's quite outdated. This PR makes it up to date and automates some of the maintenance.
Solution
Use solc from nixpkgs instead of custom flake. This will at least update solc when it's updated in nixpkgs versus remaining on the same solc version until someone manually edits flake.nix and makes a PR.
Add a CI job to ensure the nix dev env can be used to build foundry. I would like to make it possible to run all the tests too but this would requires more work to track down reasons for the individual test failures.
Example run of CI on my fork: https://github.com/sveitser/foundry/actions/runs/14489873502