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/038f5f82-ad61-48f4-958d-2fe652e46ca4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
