-
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
ci: add ability to upload wasm artefacts based on release hash #100
base: main
Are you sure you want to change the base?
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #100 +/- ##
=======================================
Coverage 97.09% 97.09%
=======================================
Files 69 69
Lines 3923 3923
=======================================
Hits 3809 3809
Misses 114 114 ☔ View full report in Codecov by Sentry. |
…rk/axelar-cgp-stellar into hash-release-process
# Once a release is done for a package, we iterate on each of these packages and build its corresponding artifacts and upload them | ||
strategy: | ||
matrix: | ||
releases: ${{ fromJson(needs.define-matrix.outputs.releases) }} |
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.
Very inefficient, we're rebuilding each contract although they're all on the same commit. Separate the build and cloudflare upload into their own reusable workflows, so the build can be run once, and cloudflare push can be done for each contract
closes AXE-6843
the new workflow is mostly adapted from
release.yaml
Test: https://github.com/axelarnetwork/axelar-cgp-soroban-testing/actions/runs/13063535201