[RelEng] Create and update maintenance branches in release preparation #3261
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
HannesWell
force-pushed
the
create-maintanance-branch-in-preparation
branch
3 times, most recently
from
5230d6a to
63dc187
Compare
HannesWell
changed the title
Member
Author
|
This is a pure RelEng change that's intended to be used for the upcoming release preparation. Therefore I'm submitting this now despite we are currently in a freeze-period. And as the verification build doesn't test this, I'm submitting this immediately. |
In the release preparation pipeline create the R4_XX_maintenance branch for the eclipse.platform.releng.aggregator repo and all submodules. Furthermore create the commit for the maintenance branch in the aggregator repo to move the maintained release's I-build to that maintenance branch and push it as PR against the maintenance branch.
HannesWell
force-pushed
the
create-maintanance-branch-in-preparation
branch
from
63dc187 to
8bfce32
Compare
Member
Author
These jobs have been deleted. |
5 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
In the release preparation pipeline create the R4_XX_maintenance branch for the
eclipse.platform.releng.aggregatorrepo and all submodules. Furthermore create the commit for the maintenance branch in the aggregator repo to move the maintained release's I-build to that maintenance branch and push it as PR against the maintenance branch.This automates changes like
and allows to delete the
Create Maintenance Branchjob and its unused back-up ep-createMaintenanceBranch from the RelEng Jenkins instance.