Hi, We are using the "Build after other projects are built" feature...
Job B is triggered to run after Job A runs. Job A is based on a CloudBees Template. The build trigger is set on Job B, not Job A. Sometimes it works correctly (i.e. Job A runs and Job B is triggered. When it works correctly, I will see something like this on a Job B run: Started by upstream project flight-review/weather-review-application-ci<http://jenkins.netjets.com/job/flight-review/job/weather-review-application-ci/> build number 308<http://jenkins.netjets.com/job/flight-review/job/weather-review-application-ci/308/> originally caused by: * Started by an SCM change<http://jenkins.netjets.com/job/flight-review/job/weather-review-application-tests/146/pollingLog> However, a lot of times, Job B does not get triggered when Job A runs successfully. Has anyone else ran into this issue? If so, any ideas what might be the problem? Thanks, Bob *** *** *** This message contains information which may be confidential and privileged. Unless you are the addressee (or authorized to receive for the addressee), you may not use, copy or disclose to anyone the message or any information contained in the message. If you have received the message in error, please advise the sender by reply e-mail and delete the message. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
