Search Gradle plugins
| Plugin | Latest Version |
|---|---|
io.github.git-commit-id.git-commit-id-gradle-plugin
CC-compatible
Capture comprehensive git repository metadata at build time -- commit ID, branch, tags, and more -- to embed in your artifacts for reproducibility and traceability. |
0.0.1
(07 April 2026) |
se.alipsa.gradle.maven-module
CC-compatible
Allows a Maven project (with a pom.xml) to participate in a Gradle multi-project build |
0.2.0
(01 April 2026) |
|
Adds a remote build cache that is configured via environment variables: - GRADLE_REMOTE_BUILD_CACHE_URL: the base URL for the remote build cache - PUSH_TO_REMOTE_BUILD_CACHE: boolean value whether to push to the remote build cache or to use it only for pulling. (optional, default: false) - MAVEN_USER: the username for the maven repository (optional) - MAVEN_PASSWORD: the password for the maven repository (optional) No remote cache is added if no GRADLE_REMOTE_BUILD_CACHE_URL is set. |
1.1.0
(23 January 2025) |
|
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) |
|
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) |
|
Docker image build, tag, and push support. Registers docker (build), dockerTag, dockerPush, dockerLogin, dockerLogout, dockerClean, and dockerCleanupImage tasks. Configure images via the docker DSL: image name, Dockerfile path, build args, labels, platforms, and additional build context files. Supports docker buildx (default) with multi-platform builds and automatic AWS ECR login. Automatically stamps images with build provenance labels (branch, commit hash, build number, repository URL). When com.stano.spring-boot is also applied, auto-configures the image name and wires bootWar output as the build context. |
0.1.6
(22 June 2026) |
|
A Gradle build cache implementation that uses Google Cloud Storage (GCS) to store the build artifacts. Since this is a settings plugin the build script snippets below won't work. Please consult the documentation at Github. |
1.4.0
(10 May 2026) |
|
A Gradle build cache implementation that uses Google Cloud Storage (GCS) to store the build artifacts. Since this is a settings plugin the build script snippets below won't work. Please consult the documentation at Github. |
1.1.0
(18 October 2021) |
|
A Gradle build cache implementation that uses Google Cloud Storage (GCS) to store the build artifacts. Since this is a settings plugin the build script snippets below won't work. Please consult the documentation at Github. |
1.0.1
(13 September 2020) |
|
A Gradle build cache implementation that uses Google Cloud Storage (GCS) to store the build artifacts. Since this is a settings plugin the build script snippets below won't work. Please consult the documentation at Github. |
1.0.2
(06 May 2020) |
