From dcc8a30f2a1cb597ebc609d10d34b45c68c9a74e Mon Sep 17 00:00:00 2001 From: Chris Dent Date: Sat, 27 Jun 2015 12:45:21 +0000 Subject: [PATCH] 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 --- doc/source/plugins.rst | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/doc/source/plugins.rst b/doc/source/plugins.rst index b166936a8b..1b6f5e36ed 100644 --- a/doc/source/plugins.rst +++ b/doc/source/plugins.rst @@ -221,7 +221,9 @@ the best practice is to build a dedicated ``stackforge/devstack-plugin-FOO`` project. 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/.yaml`` definition in +`project-config +`_:: # Because we are testing a non standard project, add the # our project repository. This makes zuul do the right