[RelEng] Include release in name of deployment to Maven Central Portal #3197
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 simplifies distinguishing deployments in case more than one was done recently.
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 simplifies distinguishing deployments in case more than one was done recently.
CC @elsazac this is what I suggest in https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/6130#note_4565661
Future deployments will have names similar to
PLATFORM_R-4.36-202505281830PDE_R-4.36-202505281830JDT_R-4.36-202505281830and the second 'tag' part must match the id of the repo that was passed to the Maven deploy job.