Re: withMaven dependency trigger - Need help to understand the error message

Ack. We need to improve the troubleshooting guide "Why my downstream job doesn't get triggered". A SQL approach could be interesting but as our queries are no trivial, there would be a risk of misunderstanding. Maybe adding a troubleshooting API/GUI/CLI on the withMaven pipeline graph is the m

Re: withMaven dependency trigger - Need help to understand the error message

I believe I don't have the scenario that you described. Mine is more like Project A, B, and C depends on D, after D builds, A, B, and C are not built So I need to troubleshoot, to see what I missed from my setup -D On Monday, March 12, 2018 at 9:00:20 AM UTC-7, Cyrille Le Clerc wrote:

Re: withMaven dependency trigger - Need help to understand the error message

> How can I troubleshoot this? I discussed this feature with Arnaud Héritier today for another use case. My understanding is that it is "work as design" and that you ask for an improvement to disable this JENKINS-46313 Avoid excessive triggering of downstream jobs

Re: withMaven dependency trigger - Need help to understand the error message

Thanks for the explanation. It is clear now In my case, I downstream should be built regardless, but it is not. How can I troubleshoot this? Thanks -D On Sunday, March 11, 2018 at 9:37:13 AM UTC-7, Cyrille Le Clerc wrote: > > Sample: projects framework, shared-lib and webapp. > > Both share

withMaven dependency trigger - Need help to understand the error message

Sample: projects framework, shared-lib and webapp. Both shared-lib and webapp depend on framework and webapp also depend on shared-lib. When framework build succeeds, it should trigger both shared-lib and webapp. But it's a "waste" to trigger webapp now because shared-lib will trigger "webapp"

withMaven dependency trigger - Need help to understand the error message

Hi I am trying to get an upstream to trigger downstream project using snapshot trigger. My upstream logs the following message [withMaven] Not triggering xx because it has dependencies in the downstream project list Could some one explain what it really mean? 'xxx' is my downst