From 2774316c838a86dc34530d83835f240d08b2437d Mon Sep 17 00:00:00 2001 From: Andreas Jaeger Date: Sun, 26 Feb 2017 19:50:07 +0100 Subject: [PATCH] Remove Jenkins mention OpenStack CI does not use Jenkins anymore, generalize the wording. Change-Id: I44c2e1f0c2e9f4dc97a553a6706275067bb104f4 --- README.rst | 4 ++-- doc/contributor-guide/source/docs-builds.rst | 10 +++++----- doc/contributor-guide/source/docs-review.rst | 5 +++-- 3 files changed, 10 insertions(+), 9 deletions(-) diff --git a/README.rst b/README.rst index a1110ce4e1..b9b1c0b26b 100644 --- a/README.rst +++ b/README.rst @@ -75,8 +75,8 @@ Testing of changes and building of the manual ============================================= Install the Python tox package and run ``tox`` from the top-level -directory to use the same tests that are done as part of our Jenkins -gating jobs. +directory to use the same tests that are done as part of the OpenStack +CI jobs. If you like to run individual tests, run: diff --git a/doc/contributor-guide/source/docs-builds.rst b/doc/contributor-guide/source/docs-builds.rst index 07babb5f3f..57db660469 100644 --- a/doc/contributor-guide/source/docs-builds.rst +++ b/doc/contributor-guide/source/docs-builds.rst @@ -119,10 +119,10 @@ https://docs.openstack.org/user-guide/. Using Tox to check builds ------------------------- -As a part of the review process, Jenkins runs gating scripts to check that -the patch is fine. Locally, you can use the Tox tool to ensure that a patch -works. To check all books, run the following command from the base directory -of repository: +As a part of the review process, the OpenStack CI system runs scripts +to check that the patch is fine. Locally, you can use the Tox tool to +ensure that a patch works. To check all books, run the following +command from the base directory of repository: .. code-block:: console @@ -190,7 +190,7 @@ The build jobs for documentation are stored in the https://git.openstack.org/cgit/openstack-infra/project-config repository. The :file:`zuul/layout.yaml` file and the ``jenkins/jobs/manual-jobs.yaml`` or ``jenkins/jobs/api-jobs.yaml`` -file contain the Jenkins build jobs that build to the docs.openstack.org +file contain the build jobs that build to the docs.openstack.org and developer.openstack.org sites, copying built files via FTP. The release specific books are built for the currently supported branches diff --git a/doc/contributor-guide/source/docs-review.rst b/doc/contributor-guide/source/docs-review.rst index b8d4cac16d..18e2fd64a4 100644 --- a/doc/contributor-guide/source/docs-review.rst +++ b/doc/contributor-guide/source/docs-review.rst @@ -55,11 +55,12 @@ Once done, follow the steps below to submit a patch review. you can also highlight the line or word in question, and press 'c' on your keyboard, which enables commenting directly on that line or word. Click :guilabel:`Save` button once you write a draft of your comment. -#. In the :guilabel:`Jenkins check` section, click the Jenkins ``checkbuild`` +#. In the :guilabel:`Jenkins check` section, click the ``checkbuild`` gate link (for the openstack-manuals, it is called ``gate-openstack-manuals-tox-doc-publish-checkbuild``) and review the built manuals to see how the change will look on the web page. For a new - patch, it takes some time before Jenkins checks appear on the Gerrit page. + patch, it takes some time before the OpenStack CI system checks appear on + the Gerrit page. You can also :ref:`build the patch locally ` if necessary. #. Click :guilabel:`Reply` to vote and enter any comments about your review,