| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
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 <tbramwell@linuxfoundation.org>
|
|
Since we don't release releng as a python project, it doesn't make much
sense to include a setup.py.
The jjb testenv in tox.ini is modified to pin jenkins-job-builder and no
longer require setup.py nor jjb/test-requirements.txt, and the modules
testenv is moved to it's own tox.ini under modules.
Locally testing of jjb can still be done using:
tox -e jjb
Change-Id: I512b1a8f9cd7d48a2f14b1bbe966b525793a6fe3
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
be easier to test jjb locally before submit for review.
add unitest in modules dir to tox(tox -emodules)
Change-Id: Ief4f10debc567d1d3ba111685c86b812a2058697
Signed-off-by: Julien <zhang.jun3g@zte.com.cn>
|
Trevor Bramwell
Julien