-
Notifications
You must be signed in to change notification settings - Fork 768
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release frame-omni-bencher
#4354
Comments
How long is the build time? @EgorPopelyaev do you know what would be the steps to attach another binary to the release? |
@ggwpez https://github.com/polkadot-fellows/runtimes/actions/runs/8923074053/job/24506630345?pr=298#step:11:1001
|
ok, thank you, I will check later, |
@EgorPopelyaev I added job that should build that binary here: https://github.com/paritytech/polkadot-sdk/pull/4405/files#diff-56213afe4ff9406795cf7f877c62e3f277dc7edaeccef4a26260f50f776663f0 |
would it not be possible to create a CI image that already has this stuff installed? That seems like the more correct solution to me. |
Closes: #4354 This PR adds the steps to build and attach `frame-omni-bencher` and `chain-spec-builder` binaries to the release draft ## TODO - [x] add also chain-spec-builder binary - [ ] ~~check/investigate Kian's comment: `chain spec builder. Ideally I want it to match the version of the sp-genesis-builder crate`~~ see [comment](#4518 (comment)) - [ ] Backport to `polkadot-sdk@1.11` release, so we can use it for next fellows release: polkadot-fellows/runtimes#324 - [ ] Backport to `polkadot-sdk@1.12` release --------- Co-authored-by: Branislav Kontur <bkontur@gmail.com>
Closes: #4354 This PR adds the steps to build and attach `frame-omni-bencher` and `chain-spec-builder` binaries to the release draft ## TODO - [x] add also chain-spec-builder binary - [ ] ~~check/investigate Kian's comment: `chain spec builder. Ideally I want it to match the version of the sp-genesis-builder crate`~~ see [comment](#4518 (comment)) - [ ] Backport to `polkadot-sdk@1.11` release, so we can use it for next fellows release: polkadot-fellows/runtimes#324 - [ ] Backport to `polkadot-sdk@1.12` release --------- Co-authored-by: Branislav Kontur <bkontur@gmail.com>
Closes: #4354 This PR adds the steps to build and attach `frame-omni-bencher` and `chain-spec-builder` binaries to the release draft ## TODO - [x] add also chain-spec-builder binary - [ ] ~~check/investigate Kian's comment: `chain spec builder. Ideally I want it to match the version of the sp-genesis-builder crate`~~ see [comment](#4518 (comment)) - [ ] Backport to `polkadot-sdk@1.11` release, so we can use it for next fellows release: polkadot-fellows/runtimes#324 - [ ] Backport to `polkadot-sdk@1.12` release --------- Co-authored-by: Branislav Kontur <bkontur@gmail.com>
Closes: paritytech#4354 This PR adds the steps to build and attach `frame-omni-bencher` and `chain-spec-builder` binaries to the release draft ## TODO - [x] add also chain-spec-builder binary - [ ] ~~check/investigate Kian's comment: `chain spec builder. Ideally I want it to match the version of the sp-genesis-builder crate`~~ see [comment](paritytech#4518 (comment)) - [ ] Backport to `polkadot-sdk@1.11` release, so we can use it for next fellows release: polkadot-fellows/runtimes#324 - [ ] Backport to `polkadot-sdk@1.12` release --------- Co-authored-by: Branislav Kontur <bkontur@gmail.com>
Closes: paritytech#4354 This PR adds the steps to build and attach `frame-omni-bencher` and `chain-spec-builder` binaries to the release draft ## TODO - [x] add also chain-spec-builder binary - [ ] ~~check/investigate Kian's comment: `chain spec builder. Ideally I want it to match the version of the sp-genesis-builder crate`~~ see [comment](paritytech#4518 (comment)) - [ ] Backport to `polkadot-sdk@1.11` release, so we can use it for next fellows release: polkadot-fellows/runtimes#324 - [ ] Backport to `polkadot-sdk@1.12` release --------- Co-authored-by: Branislav Kontur <bkontur@gmail.com>
Closes: paritytech#4354 This PR adds the steps to build and attach `frame-omni-bencher` and `chain-spec-builder` binaries to the release draft ## TODO - [x] add also chain-spec-builder binary - [ ] ~~check/investigate Kian's comment: `chain spec builder. Ideally I want it to match the version of the sp-genesis-builder crate`~~ see [comment](paritytech#4518 (comment)) - [ ] Backport to `polkadot-sdk@1.11` release, so we can use it for next fellows release: polkadot-fellows/runtimes#324 - [ ] Backport to `polkadot-sdk@1.12` release --------- Co-authored-by: Branislav Kontur <bkontur@gmail.com>
I have a PoC for using
frame-omni-bencher
in the fellows repo: polkadot-fellows/runtimes#298. However, since there is no released version, I have to build it from the sources each time for every runtime pipeline, which is a waste of resources.How to re-use
frame-omni-bencher
for fellows or elsewhere:cargo install
, e.g. as we have for zepter,cargo install --locked -q zepter
polkadot-sdk
repo/release, so we just setup downloading from polkadot-sdk in fellows CI?cc: @ggwpez
The text was updated successfully, but these errors were encountered: