Automatically build and attach production and dev runtimes to GH releases #2054
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@PierreBesson could you please confirm if the dev debug runtimes have logging enabled as you requested in the issue? Runtimes have been built on my fork https://github.com/liamaharon/polkadot-sdk/releases/tag/test-6 |
chevdor
approved these changes
Oct 27, 2023
Co-authored-by: Chevdor <[email protected]>
Co-authored-by: Chevdor <[email protected]>
…m:paritytech/polkadot-sdk into liam-build-and-attach-runtimes-to-release
seadanda
approved these changes
Oct 27, 2023
EgorPopelyaev
approved these changes
Oct 27, 2023
Co-authored-by: Dónal Murray <[email protected]>
…m:paritytech/polkadot-sdk into liam-build-and-attach-runtimes-to-release
alvicsam
approved these changes
Oct 27, 2023
|
LGTM |
s0me0ne-unkn0wn
pushed a commit
that referenced
this pull request
Oct 29, 2023
…ases (#2054) Closes paritytech/release-engineering#6 Adds a new Github Workflow which on a new release being created, builds and attaches all runtimes managed in this repository in two flavours: - `dev-debug-build`: Built with the `try-runtime` feature and has logging enabled - `on-chain-release`: Built with the regular old `on-chain-release` feature The new Github Workflow could be extended in the future by the @paritytech/release-engineering team to fully automate the release process if they choose to, similar to how it is fully automated in the Fellowship repo (https://github.com/polkadot-fellows/runtimes/blob/main/.github/workflows/release.yml). The `on-chain-release` did not exist for parachains, so I added it. --- Tested on my fork: - https://github.com/liamaharon/polkadot-sdk/actions/runs/6663773523 - https://github.com/liamaharon/polkadot-sdk/releases/tag/test-6 --------- Co-authored-by: Chevdor <[email protected]> Co-authored-by: Dónal Murray <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes https://github.com/paritytech/release-engineering/issues/6
Adds a new Github Workflow which on a new release being created, builds and attaches all runtimes managed in this repository in two flavours:
dev-debug-build: Built with thetry-runtimefeature and has logging enabledon-chain-release: Built with the regular oldon-chain-releasefeatureThe new Github Workflow could be extended in the future by the @paritytech/release-engineering team to fully automate the release process if they choose to, similar to how it is fully automated in the Fellowship repo (https://github.com/polkadot-fellows/runtimes/blob/main/.github/workflows/release.yml).
The
on-chain-releasedid not exist for parachains, so I added it.Tested on my fork: