Search Gradle plugins
Plugin | Latest Version |
---|---|
org.kordamp.basilisk-buildGradle Basilisk Build Plugin |
0.2.0
(22 June 2016) |
org.kordamp.gradle.oci-build-cacheOCI Gradle BuildCache Plugin |
0.10.0
(29 November 2022) |
net.idlestate.gradle-gcs-build-cacheA 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.3.0
(22 February 2024) |
com.ridedott.gradle-gcs-build-cacheA 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) |
si.kamino.gradle-gcs-build-cacheA 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) |
com.github.tagantroy.gradle-redis-build-cacheA Gradle build cache implementation that uses Redis 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. |
0.1.0
(11 December 2019) |
javamuc.gradle-semantic-build-versioningThis 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) |
argelbargel.build-modules.moduleGradle-Plugin which allows to create a gradle-build which ties together multiple otherwise separate gradle-projects. It's use-case is quite similar to that of gradle's own Composite builds. |
0.5.2
(09 August 2018) |
au.id.jpg.gradle-gcs-build-cacheA 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) |
io.github.alperbry.build-trackerGradle plugin to track gradle project build insights. |
0.1alpha3
(19 May 2022) |