Jenkins is a continuous integration (CI) server. It is in use on Eclipse servers for Eclipse projects as part of the Common Build Infrastructure (CBI). This page is about the hosted service at Eclipse.org. For more information on the project itself, or to download Jenkins, please see the Jenkins project page.
Since Hudson is not maintained anymore, Jenkins is the replacement for it. They share a common ancestry, but have diverged in the past. Eventually all Hudson Instances Per Project (HIPP) will be completely replaced by Jenkins Instances Per Project (JIPP). The migration will be slow in the beginning, to minimize risks and impact on the running build infrastructure.
Jenkins instances are maintained by the Eclipse Webmasters/Release Engineer. The Jenkinsn CI servers are available here:
- Jenkins Instance Per Project (JIPP): https://ci.eclipse.org/
- TODO: also add forges
Asking for Help
- Need help setting up your instance: contact webmaster @ eclipse.org or your project mentors
- Need help actually building your code: ask your project mentors, or ask on the Common Build mailing list (cbi-dev). There are no dumb questions.
- Subscribe to cbi-dev here: https://dev.eclipse.org/mailman/listinfo/cbi-dev
Jenkins instances run on SLES12 SP1 x86_64 host machines, with 64GB RAM (hipp1 & hipp2) or 128GB RAM (hipp3-10).
Jenkins configuration and tools
Since April 2017 the proxy is no longer required to access the internet from JIPP instances. Currently outbound connections are limited to ports 80 and 443 by the firewall so there are still some restrictions.
The following plugins are installed by default. Additional plugins can be installed on request.
Differences between Hudson and Jenkins
TODO: improve this page