pla 760

[tomjohnburton]

This job will create a new chainspec if one does not already exists. It will upload the chainspec to our public S3 repo and commit the file to the repo at the release branch.

If we want to phoenix Perseverance or launch a new sisyphos, one simply needs to delete the chainspecs in the direction and then update the bootnode list.

closes pla-760

[linear]

PLA-760 Chainspecs should be created in the CI

Release branch

After the build step, we can take that binary and create a chainspec

Then we upload that chainspec to the public repo

Then we commit that chainspec to both main and the release branch, lets do via a PR at first

The CI job need only run if the <chain>.rs file changes

[codecov]

Codecov Report

Merging #4000 (f694634) into main (bf0f2d0) will increase coverage by 0%.
Report is 25 commits behind head on main.
The diff coverage is n/a.

@@           Coverage Diff           @@
##            main   #4000     +/-   ##
=======================================
  Coverage     72%     72%             
=======================================
  Files        366     368      +2     
  Lines      57289   58484   +1195     
  Branches   57289   58484   +1195     
=======================================
+ Hits       41344   42327    +983     
- Misses     13850   14061    +211     
- Partials    2095    2096      +1     

see 92 files with indirect coverage changes

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[dandanlen]

If possible can we make it open a PR or commit to a separate branch? If we do this automatically, someone should at least be aware so they can sanity-check the result.