Conversation
Adds a release build workflow, triggered by publishing a release record in the repository or by executing the workflow manually. This build is different to the normal builds in the following ways: - It skips test execution (it is expected a normal build already ran successfully for this commit before the release is finalized) - It skips verification of the generated library index (again, it is expected a normal build was already run) - A Maven version task is executed to remove the -SNAPSHOT version. Important to note: if the process is executed a second time without changing the base versions, the publish process will fail, as release builds cannot be overwritten in Github Packages.
seidewitz
changed the title
seidewitz
approved these changes
May 23, 2025
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Configuration has been added on
masterto use GiHub Actions to initiate CI builds on a push to the repository.This PR adds a release-build workflow, triggered by publishing a release record in the repository or by executing the workflow manually.
This build is different from normal builds in the following ways:
Important to note: if the process is executed a second time without changing the base versions, the publish process will fail, as release builds cannot be overwritten in GitHub Packages.