Browse code
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
Chris Dent authored on 2015/06/27 21:45:21Showing 1 changed files
| ... | ... |
@@ -221,7 +221,9 @@ the best practice is to build a dedicated |
| 221 | 221 |
``stackforge/devstack-plugin-FOO`` project. |
| 222 | 222 |
|
| 223 | 223 |
To enable a plugin to be used in a gate job, the following lines will |
| 224 |
-be needed in your project.yaml definition:: |
|
| 224 |
+be needed in your ``jenkins/jobs/<project>.yaml`` definition in |
|
| 225 |
+`project-config |
|
| 226 |
+<http://git.openstack.org/cgit/openstack-infra/project-config/>`_:: |
|
| 225 | 227 |
|
| 226 | 228 |
# Because we are testing a non standard project, add the |
| 227 | 229 |
# our project repository. This makes zuul do the right |