It could well be because we also use the Join plugin. The direct ancestor that triggered the build was not "BaselineGemStone", but the original trigger was. So, perhaps my problem is related this.
On Thu, Jan 31, 2013 at 5:35 PM, Otto Behrens <o...@finworks.biz> wrote: > Hi, > > We've recently started using the Copy Artifact Plugin (in stead of the "Copy > files into the job's workspace before building" option). Have got version > 1.25 installed on jenkins 1.500. > > Some jobs do work, but we've got the case where a job responds with "Unable > to find a build for artifact copy from: BaselineGemStone". In the config of > the job, we've got "Upstream build that triggered this job" selected, with > the project name "BaselineGemStone". > > I don't get this, because just prior to this message, it clearly says > "Started by upstream project "BaselineGemStone" build number 217". > > Am I missing something? Can you please help? > > Is there more debug info I can get? > > Thanks for a great project. Using jenkins every day. > > Otto > > -- > 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 jenkinsci-users+unsubscr...@googlegroups.com. > 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 jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
