Project better-typing

The JenkinsLint Plugin has mainly two goals:

To make it easier to detect issues in your Jenkins configuration that will cause Jenkins to blow up when you attempt to run those jobs.

To encourage discussion within the Jenkins community on the more subjective stuff. Having a set of checks to base discussion on helps drive out what we as a community think is good style.

Status	Defect Name	Description
	JobNameChecker	When creating Jenkins Jobs you must avoid whitespace. In order to comply with the style guide.
	JobDescriptionChecker	Jenkins project description might help you to know what it does and further details.
	JobAssignedLabelChecker	When setting Jenkins Jobs you should set where those Jobs can run.
	MasterLabelChecker	When setting Jenkins Jobs you should set where those Jobs can run. and avoid master label. Jenkins master shouldnt consume any CPU for building jobs.
	JobLogRotatorChecker	When setting Jenkins Jobs with some Log Rotator configuration helps to reduce the amount of disk space and speed up Jenkins UI.
	MavenJobTypeChecker	Maven job type builds considerably slowly compared to the freestyle projects. Besides of that it has its own set of bugs. Its worth to use freestyle jobs and specify the maven build wrapper instead. Open ticket.
	CleanupWorkspaceChecker	There are some builds which demand a lot of disc space. Some builds might run out of space during the build itself and cause build errors. Its recommended to wipe out those workspaces after building.
	JavadocChecker	When setting Jenkins Jobs with Javadoc post build you should either set which javadocs or remove this unused publisher phase. Otherwise the archive artifact phase may not match what you expect.
	ArtifactChecker	When setting Jenkins Jobs with Archive Artifact post build you should either set which artifacts or remove this unused publisher phase. Otherwise the archive artifact phase may not match what you expect.
	NullSCMChecker	Jenkins works fine with cron/batch tasks, Its strongly recommended to use any SCM tool and therefore to have in that repo whatever script you need to run.
	PollingSCMTriggerChecker	Polling a repository from Jenkins is inefficient; it adds delay on the order of minutes before a build starts after a commit is pushed, and it adds additional loads. It is much better instead to do push-notification from the repository.
	GitShallowChecker	When setting Jenkins Jobs with Git SCM Artifact you might speed up the cloning time if you use shallow cloning.
	MultibranchJobTypeChecker	Polling in Jenkins is inefficient, MultibranchJobProject polls for new branches and also every branch polls for new changes. Its strongly recommended to use another approach, such as: WebHooks, Configuration as Code, ...
	HardcodedScriptChecker	When setting Jenkins Jobs with Shell/Batch builds you shouldnt hardcoded the script its recommended to track them in your SCM tool instead. Otherwise you wont be able to reproduce your CI environment easily.
	GradleWrapperChecker	By distributing the wrapper with your project, anyone can work with it without needing to install Gradle beforehand. Even better, users of the build are guaranteed to use the version of Gradle that the build was designed to work with. Further details: Gradle Wrapper docs.
	TimeoutChecker	There are some builds which might hang forever and cause inaction in the build queue and slaves. Its recommended to control those time based on the build timeout plugin.
	GroovySystemExitChecker	System groovy scripts run in same JVM as Jenkins master, so theres no surprise that System.exit() kills your Jenkins master. Throwing an exception is definitely better approach how to announce some problem in the script. Further details: JENKINS-14023.
	GitRefChecker	When setting Jenkins Jobs with Git SCM you might speed up the cloning time if you use git ref repos when cloning.
	TimerTriggerChecker	When setting Jenkins Jobs with some Timer trigger configuration use the symbol H (for "hash") wherever possible to allow periodically scheduled tasks to produce even load on the system.
	GitRefSubmoduleChecker	When setting Jenkins Jobs with Git SCM you might speed up the cloning time if you use git ref repos when cloning submodules.
	BFAChecker	Categorise and analyse failed builds automatically helps to knowledge share and collaborate within a team and other teams. There are some plugins which might help you to do so, for instance: Build Failure Analyzer.
	GroovySandboxChecker	The Groovy Sandbox helps to protect the Jenkins instance from scripts which are incompetent, malicious, or both. Do not disable the Groovy Sandbox.