Changes between Version 1 and Version 2 of CI


Ignore:
Timestamp:
Oct 4, 2014, 8:47:50 PM (10 years ago)
Author:
Tim Graham
Comment:

Added more detail.

Legend:

Unmodified
Added
Removed
Modified
  • CI

    v1 v2  
    11The Jenkins continuous integration environment at http://djangoci.com is setup to build pull requests.
     2
     3
    24
    35== Commands ==
    46
    5 Whitelisted users can comment "buildbot, test this please." on a a pull request to trigger a build.
     7Admins 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.
    68
    7 Admins can comment, "buildbot, add to whitelist." to add a user to the trusted list. Whitelisted users will have their pull requests built automatically. Builds are triggered for new pull requests and when a pull request is updated.
     9Admins 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.
     10
     11The 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 [https://docs.djangoproject.com/en/dev/internals/roles/#ops-team ops team] for access.
     12
    813
    914== Troubleshooting ==
Back to Top