On Thu, Jan 15, 2015 at 2:06 PM, Jesse Glick jgl...@cloudbees.com wrote:
On Thursday, January 8, 2015 at 4:06:34 PM UTC-5, LesMikesell wrote:
b1=build( some_job)
b2=build( some_other_job, REVISION:
b1.build.properties.envVars[SVN_REVISION] )
(where REVISION is a job parameter, expanded in
On Thursday, January 8, 2015 at 4:06:34 PM UTC-5, LesMikesell wrote:
b1=build( some_job)
b2=build( some_other_job, REVISION:
b1.build.properties.envVars[SVN_REVISION] )
(where REVISION is a job parameter, expanded in the svn URL)
Well you can certainly expand variables in the ‘url’
On Thu, Jan 8, 2015 at 9:43 AM, Jesse Glick jgl...@cloudbees.com wrote:
On Wednesday, January 7, 2015 7:16:10 PM UTC-5, LesMikesell wrote:
A likely scenario would be to trigger a build from polling svn, then
building that same svn revision on several types of nodes - even if
subsequent
On Wednesday, January 7, 2015 7:16:10 PM UTC-5, LesMikesell wrote:
A likely scenario would be to trigger a build from polling svn, then
building that same svn revision on several types of nodes - even if
subsequent commits are done to the repository
Covered by:
On Thu, Jan 8, 2015 at 2:37 PM, Jesse Glick jgl...@cloudbees.com wrote:
Does this have to be different from build-flow where you could pick up
SVN_REVISION and pass it into subsequent builds
I am not very familiar with the build-flow plugin and have not heard of such
an idiom.
On Thursday, January 8, 2015 at 12:38:30 PM UTC-5, LesMikesell wrote:
Does this have to be different from build-flow where you could pick up
SVN_REVISION and pass it into subsequent builds
I am not very familiar with the build-flow plugin and have not heard of
such an idiom.
On Friday, December 19, 2014 1:06:56 PM UTC-5, LesMikesell wrote:
Is there a way to make [unartifact] address artifacts from build
(other_job) steps
https://issues.jenkins-ci.org/browse/JENKINS-24887
or track their svn revisions and build numbers?
Not quite sure what you are getting at
On Wed, Jan 7, 2015 at 6:01 PM, Jesse Glick jgl...@cloudbees.com wrote:
On Friday, December 19, 2014 1:06:56 PM UTC-5, LesMikesell wrote:
Is there a way to make [unartifact] address artifacts from build
(other_job) steps
https://issues.jenkins-ci.org/browse/JENKINS-24887
or track their
If I create a workflow with multiple node {} operations and have
step([$class: 'ArtifactArchiver', artifacts:
'**/something/*.something', fingerprint: true])
inside more than one, what is supposed to happen to duplicates?
I suppose I should try this myself instead of asking, but I haven't
gotten
On 19/12/2014 16:47, Les Mikesell wrote:
If I create a workflow with multiple node {} operations and have
step([$class: 'ArtifactArchiver', artifacts:
'**/something/*.something', fingerprint: true])
inside more than one, what is supposed to happen to duplicates?
No idea - I suggest a suck it
On 19/12/2014 16:53, James Nord wrote:
On 19/12/2014 16:47, Les Mikesell wrote:
If I create a workflow with multiple node {} operations and have
step([$class: 'ArtifactArchiver', artifacts:
'**/something/*.something', fingerprint: true])
inside more than one, what is supposed to happen to
On Fri, Dec 19, 2014 at 10:56 AM, James Nord te...@teilo.net wrote:
Also, is there a way for subsequent node{} operations to
retrieve the artifacts already archived by previous other nodes within
the same workflow build?
unarchive is your friend.
- although that name does make it sound
12 matches
Mail list logo
