Jenkins is an award-winning application that monitors executions of repeated jobs, such as building a software project or jobs run by cron. Among those things, current Jenkins focuses on the following two jobs:
Building/testing software projects continuously, just like CruiseControl or DamageControl. In a nutshell, Jenkins provides an easy-to-use so-called continuous integration system, making it easier for developers to integrate changes to the project, and making it easier for users to obtain a fresh build. The automated, continuous build increases the productivity.
Monitoring executions of externally-run jobs, such as cron jobs and procmail jobs, even those that are run on a remote machine. For example, with cron, all you receive is regular e-mails that capture the output, and it is up to you to look at them diligently and notice when it broke. Jenkins keeps those outputs and makes it easy for you to notice when something is wrong.
Jenkins offers the following features:
Easy installation: Just java -jar jenkins.war, or deploy it in a servlet container. No additional install, no database.
Easy configuration: Jenkins can be configured entirely from its friendly web GUI with extensive on-the-fly error checks and inline help. There’s no need to tweak XML manually anymore, although if you’d like to do so, you can do that, too.
Change set support: Jenkins can generate a list of changes made into the build from Subversion/CVS. This is also done in a fairly efficient fashion, to reduce the load on the repository.
Permanent links: Jenkins gives you clean readable URLs for most of its pages, including some permalinks like “latest build”/”latest successful build”, so that they can be easily linked from elsewhere.
RSS/E-mail/IM Integration: Monitor build results by RSS or e-mail to get real-time notifications on failures.
After-the-fact tagging: Builds can be tagged long after builds are completed.
JUnit/TestNG test reporting: JUnit test reports can be tabulated, summarized, and displayed with history information, such as when it started breaking, etc. History trend is plotted into a graph.
Distributed builds: Jenkins can distribute build/test loads to multiple computers. This lets you get the most out of those idle workstations sitting beneath developers’ desks.
File fingerprinting: Jenkins can keep track of which build produced which jars, and which build is using which version of jars, and so on. This works even for jars that are produced outside Jenkins, and is ideal for projects to track dependency.
Plugin Support: Jenkins can be extended via 3rd party plugins. You can write plugins to make Jenkins support tools/processes that your team uses.
Do you have any tips for using Jenkins? Please add them to this list.
Please vote up or down any tips that are already here. Thank you!
Do you know any Jenkins alternatives?
Please add the names of each tool to this list and help others to find them and try them out.
Please vote up or down any alternative so we find the most popular ones. Thank you!
We hope you enjoy Jenkins. To search for any other online tool please use our search box at the top of the page.
If you have benefited from what you have learned here we hope you will consider sharing this page with your social media friends by using one of the sharing buttons out on the left. Thank you!
If you have any questions about Jenkins please ask in the comment boxes below either Google+ or click over to Facebook. If you know lots about Jenkins or any other tool featured in The Web Tools Wiki then please let us know in the comments as well. We will connect with you and give you editing rights. We often pay regular editors for their time.