opendev/system-config
Code Issues Proposed changes

docs: update Gerrit doc links

Browse Source 
The link to the documentation about the Gerrit commands pointed
to googleconde targets which aren't available anymore.
This change points to the Gerrit docs hosted by openstack.org

Change-Id: Ib1b35c38662f822881cdcc0468c3b2adc02b29c7
This commit is contained in:
Markus Zoeller 2017-01-27 16:05:54 +01:00
parent f094b61df5
commit 73359edd2d
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/source/third_party.rst
View File

@ -111,7 +111,7 @@ be all one line per event):
For most purposes you will want to trigger on ``patchset-created`` for when a For most purposes you will want to trigger on ``patchset-created`` for when a
new patchset has been uploaded. new patchset has been uploaded.
Further documentation on how to use the events stream can be found in `Gerrit's stream event documentation page <http://gerrit-documentation.googlecode.com/svn/Documentation/2.3/cmd-stream-events.html>`_. Further documentation on how to use the events stream can be found in `Gerrit's stream event documentation page <https://review.openstack.org/Documentation/cmd-stream-events.html>`_.
Posting Result To Gerrit Posting Result To Gerrit
------------------------ ------------------------
@ -133,7 +133,7 @@ In this example ``c0ff33`` is the commit ID for the review. You can
set the verified to either `-1` or `+1` depending on whether or not it set the verified to either `-1` or `+1` depending on whether or not it
passed the tests. passed the tests.
Further documentation on the `review` command in Gerrit can be found in the `Gerrit review documentation page <http://gerrit-documentation.googlecode.com/svn/Documentation/2.3/cmd-review.html>`_. Further documentation on the `review` command in Gerrit can be found in the `Gerrit review documentation page <https://review.openstack.org/Documentation/cmd-review.html>`_.
We do suggest cautious testing of these systems and have a development Gerrit We do suggest cautious testing of these systems and have a development Gerrit
setup to test on if required. In SmokeStack's case all failures are manually setup to test on if required. In SmokeStack's case all failures are manually