Hi Are you selecting "Upstream project that triggered this build", or something like that?
I used to get this when the archived artifact was already discarded (eg. when there were many upstream builds so the slow downstream job could not catch up, and artifacts were not kept that long). The solution was to "Keep last n artifacts" where n was sufficiently high (5 in my case I think). good luck, Gergo On 14 March 2013 00:53, Z W <mpc8...@gmail.com> wrote: > Hi All > > We are having issues with copying artifacts from another project plugin. > > "Unable to access workspace for artifact copy. Slave node offline?" > > We tried resetting Jenkins and it still does work. > The slave, where the project to be copied from, is connecting to hudson. > > Is there a workaround to this ? > > Thanks all > > -- > 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.
