>
> The origin concept of jenkins is "one trigger one job". For example, the
> job "neutron-unit-test-py27" could respond a new change set from neutron
> upstream. But the truth is that a gerrit event trigger a set of jenkins
> jobs: py27-unittest, pep8-check, and many dsvm jobs...
>
> How can I co
I would encourage you to take a look at zuul but if you prefer not to use
it then I believe you can also achieve your use case just using Jenkins by
setting up multiple jobs with the same trigger. The jenkins job builder
tool will help you setup and manage those jobs.
-Khai
__
On 06/09/2015 05:33 AM, Gareth wrote:
> Hi infra team,
>
> The origin concept of jenkins is "one trigger one job". For example, the
> job "neutron-unit-test-py27" could respond a new change set from neutron
> upstream. But the truth is that a gerrit event trigger a set of jenkins
> jobs: py27-unit
Hi infra team,
The origin concept of jenkins is "one trigger one job". For example, the
job "neutron-unit-test-py27" could respond a new change set from neutron
upstream. But the truth is that a gerrit event trigger a set of jenkins
jobs: py27-unittest, pep8-check, and many dsvm jobs...
How can I
