> > 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 configure my jenkins like this? >
We use the https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Trigger+Plugin plugin to do this, we have a master jenkins job that fires on some trigger (git repo change etc), and then fires off a set of sub jobs that we want executed in response to that. (we use this via the JJB macro: http://docs.openstack.org/infra/jenkins-job-builder/builders.html#builders.trigger-builds - if you're using JJB to maintain your jobs) HTH, Simon. -- Simon McCartney E: [email protected] M: +44 7710 836 915
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
