Search Gradle plugins

Want to include your Gradle plugin here?

Plugin	Latest Version
org.siouan.frontend-jdk21 Build Javascript applications with Node, NPM, PNPM, Yarn: distribution management and package manager activation (Corepack), built-in tasks, additional task types. #corepack #frontend #node #nodejs #npm #pnpm #yarn	10.0.0 (29 November 2024)
org.siouan.frontend-jdk17 Build Javascript applications with Node, NPM, PNPM, Yarn: distribution management and package manager activation (Corepack), built-in tasks, additional task types. #corepack #frontend #node #nodejs #npm #pnpm #yarn	10.0.0 (29 November 2024)
com.fussionlabs.gradle.go-plugin The `Go-Plugin` is a Gradle plugin for Go projects. This plugin does not intend to replace Go's native dependency management system, instead this plugin focuses on replacing traditional task orchestrators like Make, offering a more versatile and reusable approach for task automation. #go #golang	0.7.0 (08 May 2024)
io.github.joleksiysurovtsev.gradle-dev-containers-starter A Gradle plugin to automate the deployment of Kafka and Zookeeper containers using Docker. It handles container creation, initialization, and network setup. With each new version, new containers and tasks will be added #kafka #docker	0.0.1 (05 September 2023)
org.unbroken-dome.test-sets A plugin for the Gradle build system that allows specifying test sets (like integration or acceptance tests). Each test set is a logical grouping of a source set, dependency configurations, and related tasks and artifacts. #test #testset	4.1.0 (09 September 2023)
de.kotka.project A Gradle plugin to drive builds in a standard way It is used to configure my projects with standard values to augment POM meta information, bintray upload, additional standard tasks, etc. This plugin is highly opinionated and provided in the hope someone else might also find use for it. #build-standardization #kotkade	1.6.0 (11 November 2015)
com.fussionlabs.gradle.docker-plugin The `docker-plugin` is a Gradle plugin created to simplify the process of building and pushing Docker images. It calls the Docker CLI directly, supports multiplatform builds and provides the ability to define custom Docker tasks. #docker	0.6.0 (26 February 2025)
software.amazon.smithy.gradle.smithy-base This plugin sets up the basic capabilities necessary for building Smithy models.Applying this plugin will create the basic source sets and configurations needed for smithyprojects. It will also create a smithy build task that will build and validate all the smithy models in the project. #smithy #api #building	1.3.0 (11 June 2025)
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. #versioning #semantic-versioning #git #build-versioning #auto-versioning #version	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. #versioning #semantic-versioning #git #build-versioning #auto-versioning #version	4.1.1 (26 July 2018)