Search Gradle plugins

Want to include your Gradle plugin here?

Plugin	Latest Version
com.sherepenko.gradle.plugin-build-version This Gradle plugin provides Semantic Versioning 2.0.0 implementation with auto-increment features #semantic-versioning #version #versioning #auto-increment	0.3.0 (01 October 2021)
com.javiersc.gradle.plugins.versioning A custom plugin for Reckon Plugin and its git versioning #versioning #reckon #git	0.1.0-rc.45 (18 June 2022)
org.ai2fit.gradle.versioning-plugin A plugin that helps to maintain a semantic versioning of the build artifacts based on the project's git repository. It uses the current branch and the latest tag to enforce naming conventions #versioning #semantic #git	2.0.2 (16 February 2024)
com.markelliot.versions Creates a task that determines available dependency and plugin upgrades for a project and produces a YAML report. Additionally provides two tasks for updating the versions in a versions.props file (nebula.dependency-recommender or com.palantir.consistent-versions compatible) and updating plugin versions in Gradle plugin blocks. #versions	0.43.0 (18 February 2023)
io.zensoft.versioning Gradle Versioning Plugin #zensoft #versioning #git #version	1.1.0 (11 February 2019)
io.freefair.git-version Git Version Plugin #git #version	8.11 (16 November 2024)
javamuc.gradle-semantic-build-versioning This 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. #versioning #semantic-versioning #git #build-versioning #auto-versioning #version	4.1.1 (26 July 2018)
com.karmanno.plugins.semver Plugin for auto increase version #version #semver #automatic-versioning	2.0.0 (08 October 2021)
io.alcide.gradle-semantic-build-versioning This 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. #versioning #semantic-versioning #git #build-versioning #auto-versioning #version	4.2.2 (13 May 2021)
io.github.anvell.versioning.gradle.plugin Gradle plugin for managing project versions via Git tags #calver #versioning #git #automation	2024.06.01 (05 June 2024)

Previous Next