Skip to content
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

170 Call Gitlab CI job to Automate Runtime Release #430

Merged
merged 27 commits into from
Jun 17, 2024

Conversation

b-yap
Copy link
Contributor

@b-yap b-yap commented Mar 12, 2024

partially closes https://github.com/pendulum-chain/tasks/issues/170.

  • added a script for picking commits related to specific runtime;
  • added a github action for srtool (based on bifrost's)
  • added a js for authorizing upgrade based on the srtool.

Full info can be found in the issue.

.github/workflows/release.yml Outdated Show resolved Hide resolved
.github/workflows/release.yml Outdated Show resolved Hide resolved
.github/workflows/release.yml Outdated Show resolved Hide resolved
.github/workflows/release.yml Outdated Show resolved Hide resolved
.github/workflows/release.yml Outdated Show resolved Hide resolved
@b-yap b-yap changed the title Workflow for Automating Runtime release Workflow for Automating Runtime release (DO NOT MERGE) Mar 20, 2024
@b-yap b-yap marked this pull request as ready for review March 20, 2024 11:06
@b-yap b-yap requested a review from a team March 20, 2024 11:07
Copy link
Contributor

@gianfra-t gianfra-t left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks very good @b-yap !! This will save us a lot of time and potential errors.
I only have one comment but it may not be feasible. Since common.js and the constants are taken from the transaction builder repo, do you think it makes sense to fetch those file as one more step in the last work? So we don't have to keep track of both of them.

I think we could just use run: curl ... but then I don't know because the repo is private.

.github/workflows/scripts/get_commits.sh Outdated Show resolved Hide resolved
Copy link
Member

@ebma ebma left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wow really cool stuff @b-yap, very impressive! I think for the .js stuff, we should strip this down and reduce the files to maybe just one as there is plenty of code we don't need. Some other changes are required to make this work in CI but it already looks great overall 🙏

Since common.js and the constants are taken from the transaction builder repo, do you think it makes sense to fetch those file as one more step in the last work? So we don't have to keep track of both of them.

Regarding this, I agree and would prefer not to link both of them but keep the code here to a minimum.

.github/workflows/release.yml Outdated Show resolved Hide resolved
.github/workflows/scripts/js/common.js Outdated Show resolved Hide resolved
Copy link
Member

@TorstenStueber TorstenStueber left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@b-yap Nice PR, this will really improve our lives.

Some major missing part is of course the creation of a GitHub release but I assume that you will add this to the GitLab CI flow?

.github/workflows/release.yml Outdated Show resolved Hide resolved
.github/workflows/release.yml Outdated Show resolved Hide resolved
.github/workflows/release.yml Outdated Show resolved Hide resolved
Copy link
Contributor

@bogdanS98 bogdanS98 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks great, good job @b-yap 👍🏼 Can't wait to see it in action! I only left some questions.

.github/workflows/release.yml Outdated Show resolved Hide resolved
.github/workflows/release.yml Outdated Show resolved Hide resolved
.github/workflows/scripts/get_commits.sh Outdated Show resolved Hide resolved
@b-yap b-yap force-pushed the task-170-automate-runtime-release-process branch from 02e822a to 4d61a1a Compare May 16, 2024 10:43
@b-yap b-yap changed the title Workflow for Automating Runtime release (DO NOT MERGE) Workflow for Automating Runtime release May 16, 2024
@b-yap
Copy link
Contributor Author

b-yap commented May 16, 2024

All the scripts have been moved to gitlab.

@b-yap b-yap changed the title Workflow for Automating Runtime release 170 Call Gitlab CI job to Automate Runtime Release May 16, 2024
@b-yap
Copy link
Contributor Author

b-yap commented May 16, 2024

@TorstenStueber

Some major missing part is of course the creation of a GitHub release but I assume that you will add this to the GitLab CI flow?

Yes, I'll leave that to Zoltan; I've already moved the scripts to gitlab. And the process should be easier over there, than this github CI.

@b-yap b-yap marked this pull request as draft May 17, 2024 06:08
@b-yap b-yap marked this pull request as ready for review May 17, 2024 10:54
@b-yap b-yap requested a review from a team May 21, 2024 05:47
Copy link
Member

@ebma ebma left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me, though I did not check the respective commands of the job in Gitlab yet.

@ebma
Copy link
Member

ebma commented Jun 13, 2024

I also checked the Gitlab code now and it all looks good to me. Let's merge this now or is there a reason not to do that yet @b-yap?

@b-yap
Copy link
Contributor Author

b-yap commented Jun 17, 2024

@ebma, I "resolved" the conversations but the Squash and merge button is still disabled. Can you try to "resolve" them and see if it works?

@ebma
Copy link
Member

ebma commented Jun 17, 2024

@b-yap should work now, at least it's all green for me.

@b-yap b-yap merged commit 29e540a into main Jun 17, 2024
3 checks passed
@b-yap b-yap deleted the task-170-automate-runtime-release-process branch June 17, 2024 09:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants