-
Notifications
You must be signed in to change notification settings - Fork 527
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
Introduce Hardfork Generation Nightly Test #15483
Conversation
!ci-nightly-me |
!ci-build-me |
1 similar comment
!ci-build-me |
!ci-build-me |
5 similar comments
!ci-build-me |
!ci-build-me |
!ci-build-me |
!ci-build-me |
!ci-build-me |
!ci-build-me |
1 similar comment
!ci-build-me |
!ci-build-me |
1 similar comment
!ci-build-me |
!ci-nightly-me |
!ci-build-me |
!ci-nightly-me |
!ci-build-me |
… tag to filter out only hardfork package items in CI
remove Release tag for
da50a24
to
570069b
Compare
!ci-build-me |
Nightly run is green regarding hardfork jobs: |
!ci-build-me |
There's a TODO here after we ship berkeley that we need to also update the hardfork pipeline config in buildkite to correctly use the new way of selecting the hardfork jobs. |
Introducing Hardfork Generation Nightly test on fixed values:
NETWORK_NAME=devnet
CONFIG_JSON_GZ_URL=https://storage.googleapis.com/tmp-hardfork-testing/fork-devnet-march-22-2024.json.gz
In order to support this mechanism, I had to refactor a bit CI code. Extracted package generation job into separate and removed PackageGeneration Mode which was IMHO a duplication for Stable one. As a consequence I introduced new tag and filter to only run Hardfork pacakge generation jobs.
We need to change also pipeline setup for manually triggered jobs:
The last change is to update our nightly scheduled config and github webhook to add above two variables