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
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 spe
I believe it's not even a plugin. One of the post build actions is to trigger
another build when the other completes.
In other words, you take off the SCM trigger off of B and tell A to fire off B
when it completes. You can also do this the other way around too. One of the
build triggers is to
I'll just add, as others have suggested, an SCM trigger in B doesn't
quite do what we need it to do, because our build environment mucks
with configuration in the system, not just a Jenkins build workspace.
What we need is a timely, stateful trigger on B that responds to A
when it finds A successfu
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 envir
