Yessir, and re: a previous reply as well, this is what we ended up doing. Thanks for the speedy reply and happy CI! :-)
----- Original Message ----- From: Sami Tikka Sent: 08/17/12 04:00 PM To: jenkinsci-users@googlegroups.com Subject: Re: Confusion over build triggers As far as I understand, the standard triggering of other projects from post-build actions does what you want. Go into A's configuration: Add post-build action -> Build other projects. Enter project name B, choose "Trigger only if build succeeds". If it doesn't, maybe you could be even more specific with your description? -- Sami mwpowellhtx <mwpowell...@gmail.com> kirjoitti 17.8.2012 kello 13.00: > Hello, > > In test and measurement verbiage, I think of a trigger as just that: see an event, respond to that event. > > Say we have two jobs: A and B. > > A runs when it sees SCM change and builds that environment. > > I'd like to schedule B when A has successfully completed a build and build the same environment but in a different configuration, possibly run some tests, etc. > > I don't want to look for the most recent build as it could be stale: hours, even days or weeks old. Only when A is actually running, and runs to completion. > > How to explain exactly? Hard to do so unless you're familiar with the pattern: trigger, particularly as I am accustomed to talking about it, i.e. T&M. > > Is there anything in the Jenkins plugin world that can do this? Or are we stuck with a chained build setup in A? > > Thanks in advance. Best regards, Michael Powell Senior Software Developer
