Avoid deploying redundant modules during the release #6320
Merged
Conversation
This file contains 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
oscerd
approved these changes
Aug 6, 2024
ppalaga
approved these changes
Aug 6, 2024
There was a problem hiding this comment.
@jamesnetherton it looks great, thanks a lot for the effort!
jamesnetherton
force-pushed
the
optimize-release
branch
from
b6059cd to
18f1a30
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 shrinks the number of modules deployed at release time from 1435 to 1274.
I ran the full release against a local Nexus instance and the output from both the
release:prepareandrelease:performstages was as expected. The list of deployed artifacts is here:https://gist.github.com/jamesnetherton/f19fcec764d08f59c39933835f3d1dfb
I also tested the release with the Quarkus Platform. It built fine and I ran a small selection of tests, which passed.
WDYT @ppalaga?