From b902878fd61feb83159a4770ccf327d532963b67 Mon Sep 17 00:00:00 2001 From: Tim Graham Date: Mon, 15 Jan 2018 21:37:54 -0500 Subject: [PATCH] Doc'd the latest state of the Jenkins pull request builders. --- docs/internals/contributing/committing-code.txt | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/docs/internals/contributing/committing-code.txt b/docs/internals/contributing/committing-code.txt index 4ce8576702..a56bf48281 100644 --- a/docs/internals/contributing/committing-code.txt +++ b/docs/internals/contributing/committing-code.txt @@ -20,11 +20,9 @@ best pull requests possible. In practice however, committers - who will likely be more familiar with the commit guidelines - may decide to bring a commit up to standard themselves. -.. note:: - - Before merging, but after reviewing, have Jenkins test the pull request by - commenting "buildbot, test this please" on the PR. - See our `Jenkins wiki page`_ for more details. +You may want to have Jenkins test the pull request with one of the pull request +builders that doesn't run automatically, such as Oracle or Selenium. See the +`Jenkins wiki page`_ for instructions. .. _Jenkins wiki page: https://code.djangoproject.com/wiki/Jenkins