Greetings, I have experienced the same problem. Where the last job through the system "greedily" becomes the parent for all jobs which utilize the same Maven projects. This breaks otherwise correct parent/child fingerprint linkage, where upstream projects being built will not trigger downstreams because the downstreams parent is now the @nighly job which only ever runs once. It's a big pain, and as far as I can remember, was introduced a few LTS ago.
-Jesse On Thu, Apr 11, 2013 at 11:43 AM, Jonathan Piron <[email protected]>wrote: > Hi, > > I'm trying to understand how fingerprint system works. I understand the > purpose but not how it works. > I have 2 maven jobs for the same project (let's say TOP) : one daily and > one nightly. > The same goes for a BOTTOM project : one daily and one nightly job. > > Currently the nightly BOTTOM and the daily TOP are "linked" with the > fingerprint system. Once a nightly BOTTOM build finished, it triggers the > daily TOP. > > I'd like the daily BOTTOM to be "linked" to the daily TOP and the nightly > BOTTOM to be linked to the nightly TOP. > > Is there a way to achieve this ? > > Thanks for your help, > > > -- > 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 [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- There are 10 types of people in this world, those that can read binary and those that can not. -- 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
