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 successfully completed.
On Aug 17, 5:00 am, mwpowellhtx <[email protected]> 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.
