Search Gradle plugins
Plugin | Latest Version |
---|---|
com.moonlitdoor.git-versionA Gradle plugin that sets various properties available for use as the version based on the git repository. |
0.1.1
(13 February 2019) |
com.moonlitdoor.git-version-configA Gradle plugin that sets various properties available for use as the version based on the git repository. |
0.1.1
(13 February 2019) |
io.datalbry.plugin.semverSimple plugin to update the gradle version property using the git history |
0.5.0
(13 April 2022) |
io.datalbry.plugin.semver.githubSimple plugin to update the gradle version property using the git history and create GitHub releases |
0.4.2
(16 March 2022) |
com.bisiach.gradle.plugins.gitversionMakes available all GitVersion properties to the gradle build (i.e. GitVersion.SemVer). Run task GitVersion for a list of all properties. Requires GitVersion installed |
1.1.1
(15 February 2021) |
com.bisiach.gradle.gitversion-pluginMakes available all GitVersion properties to the gradle build (i.e. GitVersion.SemVer). Run task GitVersion for a list of all properties. Requires GitVersion installed |
1.0.2
(24 May 2019) |
io.github.KaustubhKhati.buildinfoPlugin generates properties file that can be consumed by Spring Boot Actuator Info endpoint |
0.1.3
(22 July 2024) |
com.pasam.gradle.buildinfoPlugin generates properties file that can be consumed by Spring Boot Actuator Info endpoint |
0.1.3
(18 March 2019) |
io.alcide.gradle-semantic-build-versioningThis is a Gradle settings-plugin that provides support for semantic versioning of builds. It is quite easy to use and extremely configurable. The plugin allows you to bump the major, minor, patch or pre-release version based on the latest version, which is identified from a git tag. It also allows you to bump pre-release versions based on a scheme that you define. The version can be bumped by using version-component-specific project properties or can be bumped automatically based on the contents of a commit message. If no manual bumping is done via commit message or project property, the plugin will increment the version-component with the lowest precedence; this is usually the patch version, but can be the pre-release version if the latest version is a pre-release one. The plugin does its best to ensure that you do not accidentally violate semver rules while generating your versions; in cases where this might happen the plugin forces you to be explicit about violating these rules. As this is a settings plugin, it is applied to settings.gradle and version calculation is therefore performed right at the start of the build, before any projects are configured. This means that the project version is immediately available (almost as if it were set explicitly - which it effectively is), and will never change during the build (barring some other, external task that attempts to modify the version during the build). While the build is running, tagging or changing the project properties will not influence the version that was calculated at the start of the build. |
4.2.2
(13 May 2021) |
javamuc.gradle-semantic-build-versioningThis is a Gradle settings-plugin that provides support for semantic versioning of builds. It is quite easy to use and extremely configurable. The plugin allows you to bump the major, minor, patch or pre-release version based on the latest version, which is identified from a git tag. It also allows you to bump pre-release versions based on a scheme that you define. The version can be bumped by using version-component-specific project properties or can be bumped automatically based on the contents of a commit message. If no manual bumping is done via commit message or project property, the plugin will increment the version-component with the lowest precedence; this is usually the patch version, but can be the pre-release version if the latest version is a pre-release one. The plugin does its best to ensure that you do not accidentally violate semver rules while generating your versions; in cases where this might happen the plugin forces you to be explicit about violating these rules. As this is a settings plugin, it is applied to settings.gradle and version calculation is therefore performed right at the start of the build, before any projects are configured. This means that the project version is immediately available (almost as if it were set explicitly - which it effectively is), and will never change during the build (barring some other, external task that attempts to modify the version during the build). While the build is running, tagging or changing the project properties will not influence the version that was calculated at the start of the build. |
4.1.1
(26 July 2018) |