Sorry found the solution. The environmental variable was not visible from
the EnvInject plugin setting it? Seems to be working in other areas but
not with this plugin. I had to do a workaround. I first wrote the
variables to a file an EnvInject plugin script. Then I read it in via
groovy.
def file = new File("mypath/scripts/versions.properties")
def contents = file.getText()
def matcher = contents =~ /RELEASE_VERSION.*/
def version = matcher[0].split("=")[1]
build("compile_v" + version)
On Thursday, July 25, 2013 12:06:02 PM UTC-4, [email protected] wrote:
>
> Wondering if we can pass in an environmental variable as the job name?
>
> I.e.
>
> build("createRelease")
> build("build-release_v$NEW_RELEASE_VER")
>
>
> Little background:
>
> I've tried passing that parameter into a static job name like
> "build-release" but when you use multiple SCM's build params don't work for
> some reason. It's an open bug not sure when the fix is coming. So
> currently we have a Sync_job that creates new jenkins jobs when a new
> release is created for that particular release. Thus the reason to want to
> pass in a param to build flow plugin for the build job name.
>
> Thanks,
> D
>
--
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].
For more options, visit https://groups.google.com/groups/opt_out.
