[RelEng] Force push tags and update branches in promotion pipeline #3291
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
This allows the release tag and build-update branches to be overwritten if a very late re-spin of the release build happens, i.e. after the release was already promoted (but not yet published).
Member
Author
|
The verification build does not test this, thus I'm submitting it immediately. |
HannesWell
added a commit
to HannesWell/eclipse.platform.releng.aggregator
that referenced
this pull request
Sep 5, 2025
HannesWell
added a commit
to HannesWell/eclipse.platform.releng.aggregator
that referenced
this pull request
Sep 5, 2025
HannesWell
added a commit
to HannesWell/eclipse.platform.releng.aggregator
that referenced
this pull request
Sep 8, 2025
HannesWell
added a commit
that referenced
this pull request
Sep 8, 2025
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.
This allows the release tag and build-update branches to be overwritten if a very late re-spin of the release build happens, i.e. after the release was already promoted (but not yet published).