Search Gradle plugins

Want to include your Gradle plugin here?

Plugin	Latest Version
se.bjurr.violations.violation-comments-to-github-gradle-plugin Gradle plugin for Violation Comments to GitHub #violation	1.70.0 (26 March 2023)
se.bjurr.violations.violations-gradle-plugin Gradle that will find report files from static code analysis, present and optionally fail the build. #violation #static code analysis #checkstyle #cpplint #cppcheck #csslint #findbugs #flake8 #pylint #pep8 #mccabe #pyflakes #jshint #lint #perlcritic #pmd #resharper #xmllint	3.0.2 (09 November 2024)
se.bjurr.violations.violation-comments-to-gitlab-gradle-plugin Gradle plugin that will comment GitLab merge requests with results from static code analysis #violation #static code analysis #checkstyle #cpplint #cppcheck #csslint #findbugs #flake8 #pylint #pep8 #mccabe #pyflakes #jshint #lint #perlcritic #pmd #resharper #xmllint	1.41.3 (06 July 2021)
io.github.bjornvester.codenarcprinter A plugin that prints CodeNarc violations to the console at QUIET level #codenarc	1.1 (14 November 2023)
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)
org.ec4j.editorconfig A Gradle plugin for checking whether project files comply with format rules defined in .editorconfig files and eventually also for fixing the violations #editorconfig #lint	0.1.0 (25 January 2024)
com.autonomousapps.plugin-best-practices-plugin Gradle Plugin that detects violations of Gradle best practices in Gradle Plugins #best practices	0.10 (17 July 2023)