Merge "Clarify meaning of Jenkins master configuration settings in target"
This commit is contained in:
commit
0a7778743a
@ -511,9 +511,14 @@ across all of the targets which are on-line::
|
||||
API key generated by Jenkins (not the user password).
|
||||
|
||||
``credentials-id`` (optional)
|
||||
If provided, Nodepool will configure the Jenkins slave to use the Jenkins
|
||||
credential identified by that ID, otherwise it will use the username and
|
||||
ssh keys configured in the image.
|
||||
This credential is used by the Jenkins Master to login to the configured
|
||||
Slaves.
|
||||
|
||||
If provided, it is used by the Jenkins Master to log in to the Jenkins
|
||||
Slaves. This id is a Jenkins credential identified by that ID. If not
|
||||
provided it will use the username and ssh keys configured in the image
|
||||
instead. In this case ensure that the path to the ssh keys exist on the
|
||||
Jenkins Master system as well as your Nodepool system.
|
||||
|
||||
``test-job`` (optional)
|
||||
Setting this would cause a newly created instance to be in a TEST state.
|
||||
|
Loading…
x
Reference in New Issue
Block a user