Re: Current build artifact

I had followed your step 3 (ls -ltr | tail -1) but just wanted to know any other options. I will explore your suggestion mentioned in step 2, thanks for it. Regards, Seenu. On Monday, 8 July 2013 22:33:36 UTC+5:30, Eric Pyle wrote: > > Some thoughts: > > 1) If I understand correctly, in you

Re: Current build artifact

Some thoughts: 1) If I understand correctly, in your step 1 you run a Maven snapshot build, which creates some artifacts. Assuming you are using a Nexus repository, you can have step 2 download the required artifact from Nexus. You can find an example bash script to do that at [1]. 2) You co

Re: Current build artifact

Sorry for not being clear in articulating my requirement if my first mail: 1) In step 1 of my build plan, I have maven generate the following file: /var/lib/jenkins/jobs/myjob/modules/org.opendaylight.controller$distribution.opendaylight/builds/2013-07-05_19-01-16/archive/org.opendaylight.contr

Re: Current build artifact

All tasks within same job execution start in same directory. In such case there should not be any problems with finding build artifacts. This case is not really Jenkins specific. If you want to use artifacts of job A in job B (triggered by job A) you should use Copy Artifact Plugin

Re: Current build artifact

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, Jul

Current build artifact

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 acc