View JenkinsLint on the plugin site for more information.
Detects whether your Jenkins configuration follows those best practices This plugin has mainly two goals:
Detects whether your Jenkins configuration follows those best practices
This plugin has mainly two goals:
Jenkins is an awesome Automation System, and there are a bunch of people using it in different ways, for example: developers, testers, automation, build engineers, release engineers, scrum master, product owner and so on. Unfortunately, as the number of jobs grows, maintaining them becomes tedious, and the paradigm of no using a predefined set of best practices falls apart.
The Jenkins Lint plugin attempts to solve this problem by allowing jobs to be evaluated with some predefined best practices. The goal is for your team to be able to define those best practices to be related to their project.
Manually reviewing those jobs wouldn't be too hard, but doing the same thing all over again for every new job or for a hundred other projects is where it gets difficult and tedious. This provides a much more powerful way of analyzing them.
You can find it under
<jenkins_url>/jenkinslint or reach it via links in the sidepanel of the main page. You don't need to do anything else, just click on the Jenkins Lint link and those Lint checkers will be shown.
List of available Job checks:
- Artifact Publisher check
- CleanUp Workspace check
- Git Shallow clone check
- Javadoc Publisher check
- Job Assigned Label check
- Master Assigned Label check
- Job Description check
- Job Log Rotator check
- Job Name check
- Maven Job Type check
- Null SCM check
- Polling SCM Trigger check
- Multibranch Job Type check
- Hard-coded Script check
- Gradle Wrapper check
- Built Timeout check
- Git Ref repo check
- Groovy system exit check
- TimerTrigger Hash check
List of available Slave checks:
- Slave description check
- Slave label check
- Slave version check
- Windows slave launch check
Planned upcoming features
- Show graphs.
- Configure Checks (enabled, disabled, change severity)
- Jobs action to show those jenkins lints.
- Load checks dynamically via Jenkins.
- Load checks dynamically via Reflection.
- Define some kind of programmatically scripts.
- Check: Git Submodule ref repo check
- Check: BFA check
- Check: Cyclomatic complexity check
You can ignore a particular check by adding a trailing lint:ignore:<check name> comment to the job description.
You can retrieve jenkins lint defects by requesting the following URLs :
There are two workarounds:
- Installing Workspace Cleanup Plugin
- Upgrading the JenkinsLint version
Jenkins version 1.554.1 or newer is required.
Version 0.9.0 (Upcoming release)
Version 0.8.0 (Mar 7, 2017)
- RestAPI. (issue #41449)
- TimerTrigger 'Hash' check supporting @ (issue #42337)
- Removed dependent plugins. (issue #42383)
Version 0.7.0 (Feb 26, 2017)
- Maven and Matrix projects weren't supported when linting some defects (issue #42310)
- TimerTrigger 'Hash' check (issue #42267)
- i18 support
Version 0.6.0 (Feb 12, 2017)
- Git local ref cache repos check (issue #41528)
- Groovy system exist check (issue #38617)
- Updated pom file (infra #588)
Version 0.5.0 (Oct 1, 2015)
- Build Timeout check (issue #30725)
Version 0.4.0 (Aug 27, 2015)
- Support Jenkins lint check for Jenkins Slaves (issue #30161)
Version 0.3.0 (Jul 29, 2015)
- Gradle Wrapper check (issue #29486)
Version 0.2.0 (Jul 21, 2015)
- Health Icons plus percentage (issue #29466)
- Refactor: remove optional dependencies (issue #29545) (issue #29544) (issue #29546)
Version 0.1.2 (Jul 15, 2015)
- Some builders cannot be cast to hudson.tasks.CommandInterpreter (issue #29427)
- HardcodedScript Check supports MatrixProjects (issue #29444)
- Create unit test suite for UI
Version 0.1.1 (Jul 14, 2015)
- Project dependency with ws-cleanup plugin (issue #29418)
- New Check: Hardcoded Script check
Version 0.1.0 (Jul 12, 2015)
- Initial release