Build and Release Setup #12
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
- update build structure to use a shared build logic for the modules - introduce versioning plugin
- automatically create a release tag when push to main - automatically create a release from the tag
janniclas
force-pushed
the
feature/versioning
branch
from
add092b to
35e0786
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 PR updates the project's build logic to use shared settings through the use of buildSrc.
In future all commonly used libraries (tests, logger, kotlin version), are defined in buildSrc through the convenient plugins.
Further, an auto versioning plugin was added. This plugin is used to increment the version based on conventional commits. On push to the main branch the plugin creates a new version tag on the main branch.
Additionally, I added a release workflow, which must be triggered manually to create a commit. The workflow takes a tag version as an input and creates a release for this tag.
The benefit of this approach is that we don't have to release every tag, but still have distinct tags (versions) for every merge on the main branch.