[CI/CD] Add a pipeline to build binaries in different profiles #7496
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
…nto ep-add-binary-build-pipeline
…nto ep-add-binary-build-pipeline
EgorPopelyaev
added
the
R0-silent
alvicsam
approved these changes
Feb 6, 2025
BulatSaif
approved these changes
Feb 7, 2025
mutantcornholio
approved these changes
Feb 7, 2025
Merged
via the queue into
paritytech:master
with commit Feb 7, 2025
a484ccc
216 of 252 checks passed
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.
Recently there were some requests to build and deploy a binary, for example
polkadot, in thereleaseorproductionprofile to do some testing.So far we had only a release pipeline that could do it in the GitHub but to use it, there was a lot of extra overhead needed.
This pipeline should simplify this case and give a possibility to build a binary in desired profile from any branch for the testing purposes.
Something similar to what we have for runtimes in the srtool repo
It won't be used in any release activities though.
CC: @BulatSaif