Currently the GPII Jenkins server is set up to run tests when GitHub notifies it of changes being pushed to project repositories. This has resulted in master branches sometimes becoming unstable when breaking changes are merged in. The CI server should be set up to run tests and report failures when PRs are opened, providing more immediate feedback to contributors. Jenkins Job Builder and the GitHub Pull Request Builder Plugin will allow us to be notified of potential issues before breaking changes end up in stable branches.
- I recommend to create GitHub 'bot' user that will be used for communication with GitHub (however you can use your own account if you want).
- The user needs to have push rights for your repository (must be collaborator (user repo) or must have Push & Pull rights (organization repo)).
The following GPII JJB definitions will need to be updated: