-
Notifications
You must be signed in to change notification settings - Fork 379
Conversation
A sample run can be seen here: |
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 cool!
Might want to not run it on every push and run it for westmint, too
@@ -0,0 +1,58 @@ | |||
name: Srtool build | |||
|
|||
on: push |
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.
I don't think we want to run the workflow on every push?
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.
@s3krit Can we run it on a release? E.g. on certain branch names or tags?
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.
Yep dead simple - if you know the pattern of what cumulus release tags look like, you can match like so: https://github.com/paritytech/polkadot/blob/master/.github/workflows/publish-draft-release.yml#L7
(and swapping tag for branch if you want to react to a particular branch pattern)
Since I am off today, my prio was to have it work first so you get wasm and
blake2_256.
Sure, on push is too much. The extra runs can be cancelled manually for now
though.
The last fix i made in subwasm should make the CI as it is also pass for
westmint.
|
Co-authored-by: Alexander Popiak <alexander.popiak@gmail.com>
The first run including westmint can be seen here: https://github.com/chevdor/cumulus/actions/runs/902147585 |
This PR adds a new github workflow to the CI.
It does the following:
srtool
subwasm