Be more explicit about jenkins project config
In documentation like this (which is a huge boon) we should strive to be as explicit and helpful as possible, so this change tries to be more clear about what a project.yaml is and where one might go to create it or change it. Change-Id: Ia66a361fc7d79e511afa3ad903fffb122b86998b
This commit is contained in:
parent
e4d57d6bed
commit
dcc8a30f2a
@ -221,7 +221,9 @@ the best practice is to build a dedicated
|
|||||||
``stackforge/devstack-plugin-FOO`` project.
|
``stackforge/devstack-plugin-FOO`` project.
|
||||||
|
|
||||||
To enable a plugin to be used in a gate job, the following lines will
|
To enable a plugin to be used in a gate job, the following lines will
|
||||||
be needed in your project.yaml definition::
|
be needed in your ``jenkins/jobs/<project>.yaml`` definition in
|
||||||
|
`project-config
|
||||||
|
<http://git.openstack.org/cgit/openstack-infra/project-config/>`_::
|
||||||
|
|
||||||
# Because we are testing a non standard project, add the
|
# Because we are testing a non standard project, add the
|
||||||
# our project repository. This makes zuul do the right
|
# our project repository. This makes zuul do the right
|
||||||
|
Loading…
Reference in New Issue
Block a user