This repository was archived by the owner on Nov 15, 2023. It is now read-only.
Move update-node-template to Polkadot's pipeline#13100
Merged
paritytech-processbot[bot] merged 1 commit intoparitytech:masterfrom Jan 11, 2023
Merged
Move update-node-template to Polkadot's pipeline#13100paritytech-processbot[bot] merged 1 commit intoparitytech:masterfrom
paritytech-processbot[bot] merged 1 commit intoparitytech:masterfrom
Conversation
will be moved to polkadot's pipeline ref https://github.com/paritytech/release-engineering/issues/142
alvicsam
approved these changes
Jan 9, 2023
rcny
approved these changes
Jan 11, 2023
Contributor
Author
|
bot merge |
rossbulat
pushed a commit
that referenced
this pull request
Jan 11, 2023
will be moved to polkadot's pipeline ref https://github.com/paritytech/release-engineering/issues/142
Contributor
|
0.9.37 did not trigger a PR downstream, this is why correct? Unless the overall release strategy is changing, we want to keep this happening for sure @joao-paulo-parity . |
Contributor
Author
The job to produce the PR was triggered (https://gitlab.parity.io/parity/mirrors/polkadot/-/jobs/2282467), but it appears there's a problem with the script. I'll submit a fix shortly. |
ltfschoen
pushed a commit
to ltfschoen/substrate
that referenced
this pull request
Feb 22, 2023
will be moved to polkadot's pipeline ref https://github.com/paritytech/release-engineering/issues/142
ark0f
pushed a commit
to gear-tech/substrate
that referenced
this pull request
Feb 27, 2023
will be moved to polkadot's pipeline ref https://github.com/paritytech/release-engineering/issues/142
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
According to https://github.com/paritytech/release-engineering/issues/142
The simplest solution I found for that requirement entails moving the job to Polkadot's pipeline and triggering it on the tags of that repository (paritytech/polkadot#6522).
Alternatively we could keep the job here and trigger a remote pipeline from Polkadot to this repository (example), but the extra complexity of that solution seems unwarranted for this script.
close https://github.com/paritytech/release-engineering/issues/142