Skip to content

Conversation

@josibake
Copy link
Contributor

The primary purpose of devazoa is to enable a workflow like:

git clone <project> && cd <project>
nix develop "github:2140-dev/devazoa#project"
# or setup permanently with a .envrc file

For testing, this means we want to be sure that our flakes a) evaluate, and b) actually work for setting up the project, for each supported platform.

This adds a CI job for doing just this: clone rust-bitcoinkernel, nix develop .., and cargo test. Somewhat brittle at the moment considering its pulling in the downstream project fresh each time, so a failure could result from a change outsider our repo. Leaving whether or not to pin these to a release of the downstream project for now, only because I think that will require more careful thought.

Note: this is currently failing for x86_64-linux on main, but merging as this will make testing a fix much easier. Up until now, I can usually get it working for one platform and then it's broken for the other platform and I'm finding it quite tedious to remember to test on both (hence the CI work).

tests that the devshell works with rust-bitcoinkernel.
this kinda serves as an e2e test since this also utilises
the bitcoin-core flake. mainly meant to catch failures
on macos since this is the least likely to get tested
during development.
@josibake josibake merged commit 3fc7591 into main May 10, 2025
2 of 4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants