Hi, Thanks for your answer but it didn't solve my issue. Here is what I tried :
- erase the 4 jobs : daily.TOP, nightly.TOP, daily.BOTTOM and nightly.BOTTOM; - recreate them, all configured to perform a deploy; - configured the daily.TOP job to be build when a dependency is build (not the nightly one) According to the election mechanism you described, as daily is alphabetically lower than nightly, I was expecting the daily.BOTTOM to be an upstream project of the daily.TOP. But actually, it's still the nightly.BOTTOM that is an upstream project of the daily.TOP !! Is there something I missed ? On Thursday, April 11, 2013 7:06:52 PM UTC+2, kutzi wrote: > > I think you're referring to the changes I had done some time ago. > Previously (before my changes) the relationship was built up to a > 'non-predictable' job (means the assigment was stable, but not really > deducable from parameters which are visible from the outside - i.e. only > based on a hashcode) > > Now it is based on the following rules: > - jobs who 'deploy' artifacts come 1st > - jobs who 'install' artifacts come 2nd > - all others come 3rd > > if there is no clear winner based on that, the alphabetical 1st job wins > > If think (hope) that I have documented that somewhere in the online > help. If not, please kick me, so I do it. > > cheers > Christoph > > Am 11.04.2013 17:51, schrieb Jesse Farinacci: > > 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] <javascript:> > > <mailto:[email protected]<javascript:>>> > 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] <javascript:> > > <mailto:jenkinsci-users%[email protected] <javascript:>>. > > > 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] <javascript:>. > > For more options, visit https://groups.google.com/groups/opt_out. > > > > > > -- 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.
