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 svn revisions and build numbers?
>
>
> Not quite sure what you are getting at here.
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, then pulling all the
build artifacts for that revision into the parent job's artifact
archive on the master - so from the one jenkins job page.you could
grab binaries built on all the different node types and ensure that
they were built from the same source. For library components you
might construct an include tree along with the binaries for different
architectures.
--
Les Mikesell
lesmikes...@gmail.com
--
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.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/CAOAgVpx4bYnCeK8Ju5FqHx2gDL8gy6jWtzL-7Bdj994_9yvb6g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
