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

ci: Regenerate Plonk artifacts on push: dev #189

Open
wants to merge 3 commits into
base: dev
Choose a base branch
from

Conversation

samuelburnham
Copy link
Member

@samuelburnham samuelburnham commented Oct 17, 2024

  • Regenerates new Plonk artifacts and uploads to S3 on every push to dev
  • Adds a manual workflow_dispatch option to release new artifacts with a custom name, e.g. v1.0.0-testnet.tar.gz

Succesful runs

Note

Artifact generation takes up to 30 minutes on a 32 vCPU Warpbuild runner. If performance is a concern, this could be reduced by 10-15 minutes with a more expensive AWS runner.

@samuelburnham samuelburnham changed the title ci: Regnerate Plonk artifacts on push: dev ci: Regenerate Plonk artifacts on push: dev Oct 17, 2024
@samuelburnham samuelburnham force-pushed the ci-plonk-artifacts branch 2 times, most recently from 3aace51 to a807715 Compare October 17, 2024 17:59
@samuelburnham samuelburnham force-pushed the ci-plonk-artifacts branch 4 times, most recently from 147dcd9 to 0bb05c3 Compare October 18, 2024 15:29
Copy link
Member

@huitseeker huitseeker left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is great, but the trigger on every push to dev is a bit too much.
The source of truth for the circuit version is here:

pub const SPHINX_CIRCUIT_VERSION: &str = "v1.0.8.3-testnet";

Would it make more sense to trigger the workflow either manually, or on every push that changed this value?
We can reasonably assume that in this case we would configure the repo to only squash-merge.

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