Search Gradle plugins
| Plugin | Latest Version |
|---|---|
nebula.gradle-scmBase SCM Plugin for gathering information or performing actions |
5.0.0
(11 December 2018) |
com.github.rmee.terraformAccess to Terraform command line client to perform cloud deployments. |
0.8.20181101124911
(01 November 2018) |
com.monits.staticCodeAnalysisConfigures PMD, CPD, Checkstyle ad Finbugs out of the box for Android and Java projects beyond defauts to improve performance and extensibility, while allowing to use remote (cacheable) configuration |
2.6.9
(19 October 2018) |
net.kyori.blossomGradle plugin to perform source code token replacements in Java-based projects |
1.1.0
(09 September 2018) |
com.github.spotbugs.temporaryPerforms quality checks on your project's Java source files using SpotBugs and generates reports from these checks. This is a temporary release to support a fix for Gradle 4.10. |
1.6.4
(07 September 2018) |
net.foragerr.jmeterA gradle plugin for running jmeter tests |
1.1.0-4.0
(22 August 2018) |
net.rdrei.android.buildtimetrackerGradle plugin to continuously track and report your build times. |
0.11.0
(10 August 2018) |
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) |
io.github.lhotari.buildsizePlugin for generating JSON that shows build size and structure but doesn't reveal content. Names are masked. |
0.5
(11 April 2018) |
uk.co.automatictester.lightningIntegrate JMeter non-functional tests with CI/CD server |
1.2.0
(30 March 2018) |