Assuming that you are still in the same job, you should be able to
reference WORKSPACE variable which point to the root of your build's
workspace. From there hopefully you have a fairly static path to reference
the files that would become artifacts at the end of the job.
Richard.
On Saturday, July 6, 2013, Srinivasa TN wrote:
> Hi All,
> My build plan consists of both which compiles and later do some
> operations on those artifacts using shell commads (using Execute Shell).
> But I am not finding how to reliable refer to the artifacts of the current
> build (I tried using BUILD_ID environment variable in the path when
> accessing the files related to project but it is not reliable - there may
> be some difference in the time build starts and the file creation and hence
> both will not have the same value). Any ideas?
>
> Regards,
> Seenu.
>
> --
> 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 <javascript:_e({},
> 'cvml', 'jenkinsci-users%2bunsubscr...@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.
