[Automation Enhancement]: Add bump version script; Make version release more automated #4372
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
volcano-sh-bot
added
the
kind/feature
Member
Author
|
/cc @Monokaix |
volcano-sh-bot
added
the
size/L
JesseStutler
force-pushed
the
bump_version_auto
branch
from
2dfc0e3 to
3e3f5f2
Compare
3 tasks
… more automate Signed-off-by: JesseStutler <[email protected]>
JesseStutler
force-pushed
the
bump_version_auto
branch
from
3e3f5f2 to
63ccff8
Compare
Member
Author
|
Now when master needs to pre-release a TAG, |
… more automate Signed-off-by: JesseStutler <[email protected]>
Member
|
/approve |
Contributor
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Monokaix The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
volcano-sh-bot
added
the
approved
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
/kind feature
What this PR does / why we need it:
Before releasing a version, Volcano usually needs to submit a PR to manually replace the hard-coded version number in the repository, such as: #4337. This is troublesome and easy to miss some files. Currently, a
bump-version.shis added to help automatically submit a PR to GitHub. The sample PR is: #4371.This script refers to cherry_pick_pull.sh, and the usage example is as follows:
The script accepts two parameters, the first is the target branch, and the second is the version number to be released. Of course, this script assumes that the repo name of
volcano-sh/volcanois upstream, and the repo name of your fork repo is origin. If the name you configure is different, the script can be:And if you don't wish to automatically raise a PR, you can add
DRY_RUN=1env to run it.Other changes:
.release-versionfile, default configuration islatest, when we need to release a new version,bump-version.shwill replace the value in the.release-versionfile, and then chart.yaml, code_verify.yaml, e2e_spark.yaml and other files will read the version number from the fileTAGenvironment variable when we need to runmake generate-yaml. And I fix some error configurations: For example, theRELEASE_TAGenvironment variable prompted incheck-generated-yaml.shdoes not actually exist ingenerate-yaml.sh.Makefilewill read the TAG definition ofMakefile.defand exports it as a global variablemake update-development-yamlto generate this file. The tutorial to deploy the monitoring in README.md also change.Which issue(s) this PR fixes:
Related #4357
Special notes for your reviewer:
NONE
Does this PR introduce a user-facing change?