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 start a build when another one completes. So, B to be triggered when A completes. Another thing you can do is locks and latches (which is a plugin). Locks and Latches prevents one project from building when another one is running. For example, A uses a database for testing, and B uses the same database. If they both hit the database at the same time, the tests will fail. You can put A and B on the same "Lock", so B won't start until A is finished and visa versa. Will either of those work for you? You can also try the Promotion plugin. This can promote a build when it passes certain tests. One of the things a promoted build can do is trigger another job. So, A could be "promoted" when it passes certain tests, and trigger B to start building. On Aug 17, 2012, at 6:00 AM, mwpowellhtx <mwpowell...@gmail.com> wrote: > 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.
