Add JReleaser and workflows #411
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
gounthar
approved these changes
Dec 7, 2024
jonesbusy
commented
Dec 7, 2024
This was referenced Dec 7, 2024
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 is a requirement for #239 (Homebrew distribution)
I did some test from my machine but didn't fully test the workflow until merged on main
The idea is
cdworkflow that create the release, upload to artifactory (I need to optimize to only deploy the parent pom and core module. The CLI is a far jar of ~100Mib and is a waste of resource to deploy it to Artifactory Jenkinsjreleaseto distribute the CLI jar on github (this is this PR) and homebrewjrelease is configured to not overide the release or changelog but only upload assets
I will perform more tests when merged