Difference between revisions of "Jenkins"
(→HIPP to JIPP migration (HIPP2JIPP))
|Line 67:||Line 67:|
|Line 74:||Line 75:|
|Line 83:||Line 86:|
|Line 104:||Line 108:|
|Line 117:||Line 122:|
Revision as of 19:34, 20 November 2017
- 1 About Jenkins
- 2 General Information
- 3 Jenkins hardware
- 4 Jenkins configuration and tools
- 5 Differences between Hudson and Jenkins
- 6 HIPP to JIPP migration (HIPP2JIPP)
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 (see HIPP2JIPP migration)
Jenkins instances are maintained by the Eclipse Webmasters/Release Engineer. The Jenkins CI servers are available here:
- List of Jenkins Instances Per Project (JIPP): https://ci.eclipse.org/
- TODO: also add forges
Asking for Help
- 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
Requesting a JIPP instance
Please file a bug against Eclipse Foundation > Community > Hudson to request your project's own instance. Please ensure your project lead can +1 the request. Please specify if you wish to grant write access to your download or code repositories.
Jenkins instances run on SLES12 SP1 x86_64 host machines, with 64GB RAM (hipp1 & hipp2) or 128GB RAM (hipp3-10).
Jenkins configuration and tools
Check CI best practices for general recommendations how to setup Jenkins.
Tools (and locations)
Build tools like JDK, Maven, Ant and Gradle are already configured in every Jenkins instance.
- jdk9-latest (/shared/common/jdk-9_x64-latest)
- jdk1.8.0-latest (/shared/common/jdk1.8.0_x64-latest)
- jdk1.7.0-latest (/shared/common/jdk1.7.0-latest)
- jdk1.6.0-latest (/shared/common/jdk1.6.0-latest)
- jdk1.5.0-latest (/shared/common/jdk1.5.0-latest)
- apache-maven-latest (/shared/common/apache-maven-latest)
- apache-maven-3.0.5 (/shared/common/apache-maven-3.0.5)
- apache-ant-1.9.6 (/shared/common/apache-ant-1.9.6)
- gradle-latest (/shared/common/gradle-latest)
- gradle-3.1 (/shared/common/gradle-3.1)
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.
Setup for specific plugins
GitHub Pull Request Builder Plugin
The GitHub Pull Request Builder Plugin (GHPRB) allows to build/test pull requests and provide immediate feedback in the pull request on GitHub.
To set this up, please open a Bugzilla issue against the Hudson component and request this feature.
Here are some details about what happens during the setup process:
- The GHPRB plugin is installed in the JIPP.
- Webmaster creates a GitHub bot user and adds it to the respective team on GitHub.
- The credentials of the GitHub bot user are added to the JIPP (with user name and password, because SSH keys are not recommended/supported by the plugin).
- The GHPRB plugin's main config is set up.
Once the ticket is resolved you should be able to configure and use the GHPRB plugin in your jobs.
Instructions how to set up GHPRB plugin in jobs can be found here: https://github.com/jenkinsci/ghprb-plugin/blob/master/README.md
Please note: Currently we don't recommend to use the 'Use github hooks for build triggering' option. Instead, with this option turned off, Jenkins is polling GitHub instead. Which should work just fine in most cases.
More info can be found in the GitHub readme: https://github.com/jenkinsci/ghprb-plugin/blob/master/README.md
Differences between Hudson and Jenkins
|Job templates "cascading"||built-in||only rudimentary with plugins|
|GitHub pull request builder plugin||No||Yes|
HIPP to JIPP migration (HIPP2JIPP)
All Hudson masters will be gradually migrated to Jenkins (this should be done in late Q1-early Q2 of 2018).
We are currently improving our tooling to automate the migration. In the meantime we are migrating individual HIPPs on request. To request a migration please open a Bugzilla issue against the Hudson component. Your place in the queue will depend on the complexity of your HIPP (amount of jobs, use of exotic plugins or build configurations).
Preparations for a migration:
- We recommend to use the migration as an opportunity to clean up your HIPP. Please check for old/deprecated build jobs that can be deleted, etc.
- Since the "cascading job" feature of Hudson is not supported in Jenkins, such jobs will need to be converted to normal jobs first.
The following tool is used to convert the configuration XMLs to a format that Jenkins understands: https://github.com/eclipse/hipp2jipp
In most cases the migration should work straight-forward and configurations are converted without any problems. Nevertheless backups are created and can be made available on request if configurations are lost.
Some know issues are listed here: https://github.com/eclipse/hipp2jipp#known-issues
TODO: improve this page