Jenkins Best Practices

Original: http://www.cnblogs.com/itech/archive/2011/11/14/2248460.html

Jenkins best practices, in fact, are the same for most other CI tools:

* Jenkins is safe. Use authorization and access control for users of Jenkins. By default Jenkins does not perform any security checks, which means that anyone can access Jenkins to configure Jenkins, modify the job, and execute the build. This may be acceptable for use within the enterprise, but there is a high security risk, such as someone else mistakenly dropping the job, incorrectly configuring your job to run every minute, booting too many builds, and so on. So the general use of plugin to add authorization and access control to Jenkins.

* A regular backup of Jenkins ' home directory.

* Use file fingerprinting to manage dependencies. When your job relies on other jobs on Jenkins, you can use file fingerprinting to help locate dependent version information.

* The most reliable build is clean Builds,clean builds means all the 3rd Party,build scripts associated with the build, release notes, etc. all need to be in source code control.

* Close integration with the issue tracking system, such as Jira or Bugzilla, has never been reduced to change log modification.

* Close integration with repository browsing tools, such as Fisheye if you use subversion as the source Code management tool.

* Always configure the job to generate trending reports and automated tests when you run a Java build. Trend reports help project managers and developers quickly understand the progress and status of current projects.

* Make sure that Jenkins ' home directory has enough space.

* Please archive the unused job before deleting it.

* Establish different job,build for different branch to detect errors as early as possible.

* Allocate different ports for parallel project builds to avoid conflicts encountered when multiple jobs are started at the same time.

* Create email Aliais for developers of different projects, so that all relevant personnel of the project will be aware of the status of the project in the first time.

* Add extra steps to find the failure early. such as log check, micro-test, etc.

* For regular maintenance work can be done automatically using the job, for example, the Disk cleanup work.

* After the build succeeds to the far code Tag,label or baseline.

* Configure Jenkins Bootstrapper to update the working directory before build.

Translated from: https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+Best+Practices

Jenkins Best Practices