| Version 2 (modified by , 10 years ago) ( diff ) |
|---|
The Jenkins continuous integration environment at http://djangoci.com is setup to build pull requests.
Commands
Admins can comment "buildbot, test this please." on a a pull request to trigger a build (and whitelisted users can do so on their own PRs). Jenkins polls GitHub every 5 minutes to pickup new changes so there may be a short delay after a comment before the build is triggered. For trusted users, builds are automatically triggered for new pull requests and when a pull request is updated.
Admins can comment, "buildbot, add to whitelist." to add a user to the trusted list. Whitelisted users will have their pull requests built automatically. In general if you submit a couple of solid PRs, we'll be happy to add you to this list.
The admins list is primarily core developers and is accessible at http://djangoci.com/job/django-pull-requests/configure for those with a Jenkins account. The White list is available on the same page after clicking "Advanced". If you are doing a lot of triage work and think it'd be helpful to trigger builds, ask the ops team for access.
Troubleshooting
If:
- you force push to a branch after the initial build starts or
- a commit is pushed to master after the initial build starts
You will see an error like git checkout <hash> where hash was not the commit. Currently the only solution is to retrigger the build. There is a ticket for the issue in GitHub Pull Request Builder.