opendev/system-config
Code Issues Proposed changes

Add example of comment formatting

Browse Source 
Add a link to the regex's for comment formatting and an example of how
to format test results nicely

Change-Id: Id917161ccf5e51855acf87a87544882dcf69b14e
This commit is contained in:
Ian Wienand 2014-04-08 16:08:47 +10:00
parent 0c7e837ee5
commit e9c8a85f0d
1 changed files with 8 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
doc/source/third_party.rst
View File

@ -112,6 +112,14 @@ setup to test on if required. In SmokeStack's case all failures are manually
reviewed before getting pushed to OpenStack, whilst this may no scale it is
advisable during initial testing of the setup.
There are several triggers that gerrit will match to alter the
formatting of comments. The raw regular expressions can be seen in
`gerrit.pp <https://git.openstack.org/cgit/openstack-infra/config/tree/modules/openstack_project/manifests/gerrit.pp>`_.
For example, to have your test results formatted in the same manner as
the upstream Jenkins results, use a template for each result matching::
* test-name-no-spaces http://link.to/result : [SUCCESS|FAILURE] some comment about the test
.. _request-account-label:
Requesting a Service Account