Skip to content

[CI/CD] Add a pipeline to build binaries in different profiles#7496

Merged
EgorPopelyaev merged 11 commits intoparitytech:masterfrom
EgorPopelyaev:ep-add-binary-build-pipeline
Feb 7, 2025
Merged

[CI/CD] Add a pipeline to build binaries in different profiles#7496
EgorPopelyaev merged 11 commits intoparitytech:masterfrom
EgorPopelyaev:ep-add-binary-build-pipeline

Conversation

@EgorPopelyaev
Copy link
Copy Markdown
Contributor

Recently there were some requests to build and deploy a binary, for example polkadot, in the release or production profile 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

@EgorPopelyaev EgorPopelyaev added the R0-no-crate-publish-required The change does not require any crates to be re-published. label Feb 6, 2025
@EgorPopelyaev EgorPopelyaev requested review from a team as code owners February 6, 2025 12:24
@paritytech-review-bot paritytech-review-bot bot requested a review from a team February 6, 2025 13:03
@EgorPopelyaev EgorPopelyaev added this pull request to the merge queue Feb 7, 2025
@EgorPopelyaev
Copy link
Copy Markdown
Contributor Author

Merged via the queue into paritytech:master with commit a484ccc Feb 7, 2025
152 of 188 checks passed
@EgorPopelyaev EgorPopelyaev deleted the ep-add-binary-build-pipeline branch February 7, 2025 11:11
clangenb pushed a commit to clangenb/polkadot-sdk that referenced this pull request Feb 19, 2025
…ytech#7496)

Recently there were some requests to build and deploy a binary, for
example `polkadot`, in the `release` or `production` profile to do some
testing.
So far we had only a
[release](https://github.com/paritytech/polkadot-sdk/blob/master/.github/workflows/release-20_build-rc.yml)
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](https://github.com/paritytech/srtool/actions/workflows/manual.yml)
It won't be used in any release activities though.

CC: @BulatSaif
lexnv pushed a commit that referenced this pull request Feb 27, 2025
Recently there were some requests to build and deploy a binary, for
example `polkadot`, in the `release` or `production` profile to do some
testing.
So far we had only a
[release](https://github.com/paritytech/polkadot-sdk/blob/master/.github/workflows/release-20_build-rc.yml)
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](https://github.com/paritytech/srtool/actions/workflows/manual.yml)
It won't be used in any release activities though.

CC: @BulatSaif
EgorPopelyaev added a commit that referenced this pull request Apr 16, 2025
Recently there were some requests to build and deploy a binary, for
example `polkadot`, in the `release` or `production` profile to do some
testing.
So far we had only a
[release](https://github.com/paritytech/polkadot-sdk/blob/master/.github/workflows/release-20_build-rc.yml)
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](https://github.com/paritytech/srtool/actions/workflows/manual.yml)
It won't be used in any release activities though.

CC: @BulatSaif
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

R0-no-crate-publish-required The change does not require any crates to be re-published.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants