On Jenkins of the past, the concept of "downstream builds" was determined through the use of fingerprints. I know that has been changing as new plugins have introduced new concepts of downstream builds. The documentation may not refer to using fingerprints, but I found that using them made this feature work like you want it to.
On Wednesday, August 19, 2015 at 7:25:56 AM UTC-7, [email protected] wrote: > > Hi Jason, > > Although I'll try to play with it later, in my case in particular, I do > NOT use fingerprints. > However, help message against *"When the following downstream projects > build successfully"* field in promotion process configuration mentions > NOTHING about fingerprints: > > *This option requires that a promoted build runs the designated downstream > builds successfully. A typical use of this is to nominate downstream test > jobs, so that you know a build has good test results before it gets > promoted. Multiple jobs can be specified by separating their names by > commas.* > > > > *For example, consider a case where job xyz-test is set as the promotion > criteria of job xyz. When xyz #100 is built, this will not be promoted > right away as no xyz-test build has run yet. If you configured xyz-test as > a downstream build of xyz, the successful completion of xyz #100 would > trigger a xyz-test. When this completes successfully, xyz #100 will be > promoted (even if other xyz builds happened since then.)* > > > So, I assume it should work anyway (using only upstream-downstream > relationships between A->B->C jobs in the chain). > > BTW, this is similar thread based on description in the first posts (but > there is no solution either): > https://groups.google.com/forum/#!msg/jenkinsci-users/sYfljDWw87g/_useLnnAKY8J > > On Wednesday, August 19, 2015 at 10:03:23 PM UTC+8, Jason Swager wrote: >> >> Do you have a common file with the same fingerprint between jobs A, B, >> and C? I have used this type of promotion before. >> >> One thing you may want to check; do the fingerprints on job A show that >> the fingerprint originated in job A? And are Job B and Job C listed with >> the same fingerprint? >> >> On Wednesday, August 19, 2015 at 6:40:37 AM UTC-7, [email protected] >> wrote: >>> >>> Hi Daniel, >>> >>> I'm dealing with the same issue and created this bug report in Jenkins >>> Jira <https://issues.jenkins-ci.org/browse/JENKINS-30033>. >>> >>> If we didn't do something wrong, it is supposed to be a common issue to >>> many users. >>> I cannot find anything wrong in what I do. >>> >>> *Have you fixed this issues since then?* >>> >>> On Sunday, April 26, 2015 at 2:27:31 PM UTC+8, Daniel Hinojosa wrote: >>>> >>>> I saw another post with this issue, and it didn't see to go anywhere. >>>> >>>> I have Job A, Job B, and Job C where Job A triggers Job B on success >>>> and Job B triggers Job C on success. All artifacts are copied and all are >>>> fingerprinted. >>>> >>>> Job A has a promoted build that will trigger "When the following >>>> downstream projects build successfully" and that is the only criteria. The >>>> issue is that it only works where there is one job listed in the field and >>>> it is immediately downstream to Job A. Any other circumstance and the >>>> build does not trigger. Am I doing something wrong, like perhaps listing >>>> the project incorrectly, or is there an actual bug? >>>> >>> -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/61670b73-fed8-4871-8343-1767679076e9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
