-
Notifications
You must be signed in to change notification settings - Fork 272
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
Automate the branch entry to version increment workflow. #2601
Labels
enhancement
New Enhancement
Comments
prudhvigodithi
added
enhancement
New Enhancement
untriaged
Issues that have not yet been triaged
labels
Sep 9, 2022
Closing this issue as the related PR, to add the branch entry is merged. |
29 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe
Coming from the comment #1375 (comment)
Exiting version increment workflow, works by a branch input passed to matrix array, once the branch is the array, release manager can trigger the workflow with single click, but still the branch entry is a manual process that has to be done by a release manager. This involves raising a PR to add a new release branch and get it approved before we run it.
Describe the solution you'd like
Extend the existing manifest workflow that raises an [AUTO] PR with new version by adding new version manifests and updating the check-for-build.jenkinsfile. Sample PR #2599.
Add a logic to update the version increment workflow to have the new
<MAJOR_VERSION.x>
branch entry.Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: