Search Gradle plugins

Plugin Latest Version

com.novoda.build-properties

A Gradle plugin to consume external build properties.

0.4.1
(17 April 2018)

com.avito.android.build-properties

Avito Android Plugin

2020.2.5
(07 February 2020)

com.sidneysimmons.gradle-plugin-external-properties

gradle-plugin-external-properties is a custom gradle plugin for loading external properties into your gradle build.

1.0.1
(21 July 2020)

org.niksi.properties

This plugin gives you control on project properties

0.0.3
(13 March 2016)

com.guidovezzoni.smartproperties

Manage build parameters from a *.property file or environment variables

0.5.1-beta
(04 May 2020)

com.guidovezzoni.hyperprop

Manage build parameters from a *.property file or an environment variables

0.2.0-beta
(15 March 2020)

org.kordamp.gradle.build-info

Defines common build properties

0.39.0
(28 June 2020)

com.bisiach.gradle.gitversion-plugin

Makes 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.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.1
(07 April 2020)

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)