From 4dc3dec04452f7ac20340f2a4790f2f2a3470b8c Mon Sep 17 00:00:00 2001 From: Trevor Bramwell Date: Wed, 4 Apr 2018 13:02:35 -0700 Subject: Update Tox JJB Command This allows using the command to only test one project's changes. For example: tox -e jjb -- jjb/releng Will only test jobs under 'jjb/releng'. If jobs have dependencies, of multiple project jobs need to be tested, they can be included using the jjb ':' syntax, as anything after '--' is passed directly to jjb: tox -e jjb -- jjb/doctor:jjb/functest Change-Id: I4b71803a1d6ed4f62d50cdca87183a68b20fae5a Signed-off-by: Trevor Bramwell --- docs/infra/jenkins/jjb-usage.rst | 6 ++++++ 1 file changed, 6 insertions(+) (limited to 'docs') diff --git a/docs/infra/jenkins/jjb-usage.rst b/docs/infra/jenkins/jjb-usage.rst index 2be2598d9..671278121 100644 --- a/docs/infra/jenkins/jjb-usage.rst +++ b/docs/infra/jenkins/jjb-usage.rst @@ -31,6 +31,12 @@ Test with tox:: tox -v -ejjb +.. note:: You can also test the jobs under a single jjb directory by + specifying the directory. For example to test only the releng jobs, you + could run: + + tox -v -e jjb -- jjb/releng + Submit the change to gerrit:: git review -v -- cgit 1.2.3-korg