Search Gradle plugins

Plugin Latest Version


A Gradle plugin for Android project, used to incrementally compile class and generate incremental DEX, much faster than the [assembleDebug] task.

(19 July 2021)


This Gradle plugin provides Semantic Versioning 2.0.0 implementation with auto-increment features

(01 October 2021)


A Gradle Plugin that supports Lint increment scanning.

(27 May 2021)

Incrementally build Pull Requests based on Git history

(14 June 2020)


Incremental Scanning for Lint !

(17 December 2018)


This plugin incrementally updates any relational databases in simple and lightweight way

(30 June 2017)


Plugin for incrementing version in git flow. Forked from

(21 December 2021)


Drag some of the things NPM gives by default into Java land. Version increment targets, Docker build and push targets.

(21 July 2021)


Increments version automatically for easy releases from CI

(15 June 2021)


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.

(13 May 2021)