opendev/system-config
Code Issues Proposed changes

Clarifies that CI accounts must request accounts from infra

Browse Source 
Currently there is ambiguity in the third party documentation
around requesting accounts. Some have interpreted the documentation
as stating it is possible to conduct tests using a gerrit user
account. This patch addresses the documentation language making
it clear that a third party ci system is required for third party
ci interactions with gerrit and the system must be created by
infra.

This patch also changes the recommended method of requesting a
third party ci account from three choices (email, bug or irc) to
one choice (email). This edit was previously part of
https://review.openstack.org/#/c/101013/ and has been moved into
this patch.

Change-Id: Iab88b729d714dcaa881376e9237834e877acecfa
This commit is contained in:
Anita Kuno 2014-06-25 10:12:45 -04:00
parent 4d668437c2
commit bb305f8719
1 changed files with 11 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
doc/source/third_party.rst
View File

@ -126,17 +126,21 @@ the upstream Jenkins results, use a template for each result matching::
Requesting a Service Account
----------------------------
In order to post comments as a Third Party CI System and eventually verify
your build status on Gerrit patches, you will need a dedicated Gerrit
system account. This account is created by a member of the OpenStack
Infrastructure team, you are unable to create this account yourself. This
account has no access via the GUI to modify settings.
Feel free to contact the OpenStack Infrastructure Team via
`email <mailto:openstack-infra@lists.openstack.org>`_,
`bug report <https://bugs.launchpad.net/openstack-ci/>`_
or in the #openstack-infra IRC channel to arrange setting up a dedicated user
(so your system can post reviews and vote using a system name rather than your
user name). We'll want a few additional details:
`email <mailto:openstack-infra@lists.openstack.org>`_ to arrange setting up a
dedicated account (so your system can post comments and verify build status).
We'll want a few additional details:
1. The public SSH key described above (if using OpenSSH, this would be the
full contents of the account's ~/.ssh/id_rsa.pub file after running
'ssh-keygen'). You can attach it to this bug or reply with a hyperlink to
where you've published it so I can retrieve it. This is a non-sensitive piece
'ssh-keygen'). You can attach it to the email or include a hyperlink to
where you've published it so it can be retrieved. This is a non-sensitive piece
of data, and it's safe for it to be publicly visible.
2. A preferred (short, alphanumeric) username you want to use for the new SSH