This repository has been archived by the owner on Oct 7, 2022. It is now read-only.
Automatic Continuous Delivery from CI server #103
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
szpak
changed the title
szpak
changed the title
Closed
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Automatic Continuous Delivery from CI server
This PR add an ability to automatically release the new version of embedded-consul to Maven Central from CI server, on demand. By the automation of the all manual steps needed to be performed on a local workstation, it opens an ability to release the new version every time the new features or fixes are in master.
Introduction
The release process has been implemented with the CDeliveryBoy, a Continuous Delivery plugin for Gradle. It greatly simplifies the configuration required for CD in a project, by providing sane defaults, whenever possible.
Features
Releasing
Assuming we are in master:
and wait a few (or maybe several) minutes - doing push-ups or other healthy activities - to see the artifacts in Maven Central!
Btw,
[#DO_RELEASE]can be also added to the commit with a new feature or a bug to trigger the release after push.Releasing an arbitrary version number
[#DO_RELEASE]is configured to release the new version with incremented patch number (e.g. 1.1.5 -> 1.1.6). However, CDeliveryBoy has a sophisticated mechanism to release an arbitrary version:[#DO_RELEASE][#MAJOR]- increase major version number[#DO_RELEASE][#MINOR]- increase minor version number[#DO_RELEASE][#PATCH]- increase patch version number (currently done by default)[#DO_RELEASE][#2.3.4]- provided version number (compatible with Semantic versioning)Changelog synchronisation with GitHub releases
As a bonus feature the locally provided changelog is synchronized with GitHub releases, which is very convenient for people receiving notification about new versions (e.g. with GitPunch).
Version update in README
As a part of release process the versions used in example configuration of the project in Gradle and Maven are automatically updated. No more manual version changes in README :-).
Limitations
CDeliveryBoy has been created by Marcin Zajączkowski to be used in his FOSS projects. It is currently used in multiple projects, however, it was not intended to be a general usage CD tool for everyone. As a result, it is currently in the maintenance mode with some known limitations.
No support for
maven-publishpluginCDeliveryBoy uses the
mavenplugin which currently is deprecated. As a result it might be problematic to build the project with Gradle 7+.Additional info
The changes are separated into 4 commits to make it easier to analyze applied changes. I recommend to merge with WITHOUT squashing to preserve it for further analysis.
Fixed #95, fixes #37.