ci: Prepare for v0.37 release branch#9338
Conversation
Signed-off-by: Thane Thomson <connect@thanethomson.com>
Signed-off-by: Thane Thomson <connect@thanethomson.com>
Signed-off-by: Thane Thomson <connect@thanethomson.com>
| @@ -0,0 +1,104 @@ | |||
| # Runs randomly generated E2E testnets nightly on the v0.37.x branch. | |||
There was a problem hiding this comment.
Assuming you took .github/workflows/e2e-nightly-34x.yml and mechanically adapted it.
Let me know if you did otherwise.
There was a problem hiding this comment.
It's actually a combination of .github/workflows/e2e-nightly-{main,34x}.yml, adapted for v0.37.x. The main E2E tests run more testnet groups.
There was a problem hiding this comment.
OK, checking out your branch and melding the files.
| - name: Capture git repo info | ||
| id: git-info | ||
| run: | | ||
| echo "::set-output name=branch::`git branch --show-current`" | ||
| echo "::set-output name=commit::`git rev-parse HEAD`" |
There was a problem hiding this comment.
I can't find this part in yml for main, intended?
There was a problem hiding this comment.
Yes. This is one of the parts that need to be taken from the 34x file to facilitate our Slack failure notifications.
With main it's easy because the latest commit hash and branch details are provided by GitHub through environment variables when the nightly E2E tests run.
But because we manually check out the v0.34.x / v0.37.x branches, we need to store this information in output variables during the test execution job so we can use them later during the notification jobs. If we don't do this, and we rely on those environment variables, we just get main and the latest commit hash on main, because that's where the nightly run was triggered.
Depends on #9337.
Prepare the CI to handle the v0.37 development processes, as per our release guidelines.
PR checklist
CHANGELOG_PENDING.mdupdated, or no changelog entry neededdocs/) and code comments, or nodocumentation updates needed