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. subversion-plugin *sets* $SVN_REVISION on the current build but
> does not automatically check out that revision if such a variable is set
> ahead of time.
With build-flow you pretty much have to create separate jenkins jobs
for each step which is klunky in some ways but it lets you pass
parameters and subsequently access data from other build objects:
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)
and then you could run yet another job, passing those build numbers to
b3=build( "my_artcollector_job", REVISION:
b1.build.properties.envVars["SVN_REVISION"], BUILD_SELECTOR1:
b1.build.number, BUILD_SELECTOR2: b2.build.number )
And those parameters are expanded for the copy artifact plugin to
assemble the layout you want, with the final job archiving the include
tree from its own svn checkout and the binaries copied from the
previous build jobs.
>
> In the meantime, as a workaround you could run ‘svn info’ on the master
> workspace to determine the current revision, keep this in a Groovy variable,
> and update slave workspaces to that.
I think the big picture is that if we want to eliminate the klunky
separate job definitions for every step we need a generic mechanism to
replace what you can pass into parameterized jobs and get back from
the build objects. Or does that already exist? In this scenario I'm
looking for something like a matrix build but more programatically
controlled and with a different final layout for the build artifacts.
--
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/CAOAgVpzaa-%3DCKD3NmN3ZLJO6bZpS3ymzK9hUdm7CKXOz9TgcVA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
