-
Notifications
You must be signed in to change notification settings - Fork 312
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
ci: use github actions to publish new tiup releases #1158
Conversation
This reverts commit 2ce40ed.
6a8f6fe
to
b02b7fe
Compare
Codecov Report
@@ Coverage Diff @@
## master #1158 +/- ##
==========================================
- Coverage 53.53% 46.30% -7.23%
==========================================
Files 284 284
Lines 20302 20318 +16
==========================================
- Hits 10868 9408 -1460
- Misses 7756 9438 +1682
+ Partials 1678 1472 -206
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
/lgtm |
[REVIEW NOTIFICATION] This pull request has been approved by:
To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. Reviewer can indicate their review by writing |
/merge |
This pull request has been accepted and is ready to merge. Commit hash: 8ca8a42
|
What problem does this PR solve?
Use GitHub Actions to automatically compile and publish new releases of TiUP and its builtin components.
This is also related to #1122
What is changed and how it works?
Added a new workflow
.github/workflows/release-tiup.yaml
to:ci/gh-*
for testing the CI itselfrelease-*
for staging test+staging
in the version string and build info, and are published to staging server defined by secretTIUP_SERVER_STAGING
TIUP_SERVER_PROD
So the releasing procedure in the future would be:
cherry-pick
needed commits to therelease-*
branchrelease-*
to github, and a staging build is triggered at this stepvx.y.z-rn-ghash
wherevx.y.z
is the last released version,n
is the commit count since last released version, andhash
is the hash of current commit (this version would be considered less than the last released version as per SemVer definitions)Check List
Tests
Release notes: