Search Gradle plugins

Plugin Latest Version

com.diffplug.spotless-changelog

Spotless Changelog checks that your changelog complies with the format of keepachangelog, and uses the information from **only the changelog file** to compute the version of the next release. If you want, you can use the computed version to update the changelog file, then automatically commit, tag, and push when a release is published.

3.0.2
(06 April 2023)

com.tomtom.gradle.updatechangelog

A plugin that automatically updates the version in your changelog file.

1.0.9
(08 April 2021)

com.glureau.grip

Update dynamically your files! Add a directive in your documentation and automatically include your library version, or another gradle variable, or a system environment variable, or even a file.

0.4.5
(25 April 2023)

com.github.rsuiteCMS.gradlePhantomjsAssistant

Gradle plugin to configure PhantomJS for automated testing. Automatically finds the requested version of PhantomJS for the running platform, downloads it, and configures the `test` task to make use of the binary.

0.4
(21 October 2015)

com.github.RSuiteCMS.gradlePhantomjsAssistant

Gradle plugin to configure PhantomJS for automated testing. Automatically finds the requested version of PhantomJS for the running platform, downloads it, and configures the `test` task to make use of the binary.

0.1-alpha
(21 October 2015)

sh.nothing.auto-debug-suffix

Automatically add DEBUG suffix on version and package name of Android app

0.1.2
(01 August 2019)

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.

4.2.2
(13 May 2021)

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.

4.1.1
(26 July 2018)

emetriq.changelog-release

Creating a semi-automatic changelog on top of nebula release plugin

1.4.0
(29 December 2017)

com.github.deckyfx.gdgengradle

Create greendao3 Model automatically on build its read from JSON file schema, and also handle version upgrade migration

1.0.8
(12 May 2019)