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’ passed to an ‘svn’ step in Workflow. As I mentioned, there is not yet support for picking up $SVN_REVISION after an initial checkout (would require API changes in Jenkins core, followed by matching changes in the Subversion plugin; or a new feature in Workflow to use scm-api-plugin); but at worst you can run ‘svn info’ to get this in the meantime. (Whether it will correctly detect the checkout as being of the same repository from build to build, despite having a different @123 in the URL, is another question. This is up to SubversionSCM.getKey.) As a separate matter, for those flows which _do_ wish to continue using the ‘build’ step rather than inlining all steps directly into the flow, it would be useful to be able to pick up build variables from the downstream freestyle build. I made a note of that in JENKINS-25851. -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/3ada0a6c-e77b-4bd7-81c4-a5c678332e57%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
