Well... it was probably too trivial for most people here to have an answer
;)
So, I give me the answer.
One possible way of doing is to create a starter freestyle job which passes
the property file to the build flow job using parameterized trigger.
Then, configure the build flow job :
// Get all env data
buildEnv=build.getEnvironment();
// Pass to any job you want to build :
build(buildEnv, "MyJob");
Le mardi 19 novembre 2013 15:12:05 UTC+1, Jean-Luc Pinardon a écrit :
>
> Let's consider this simple example :
>
> parallel (
> // job 1, 2 and 3 will be scheduled in parallel. { build("job1") },
> { build("job2") },
> { build("job3") }
> )
>
> It is possible to pass some predifined like parameters using :
> parallel (
> // job 1, 2 and 3 will be scheduled in parallel. {
> build("job1",param1:"foo",param2,"bar") },
> { build("job2",param1:"foo",param2,"bar") },
> { build("job3",param1:"foo",param2,"bar") }
> )
>
> But if I have a large set of parameters set within a file I'd like to pass
> the file.
> As the envinject plugin is installed, I can configure the property file
> within the "prepare an environment for the run" section...
> But I don't know how to pass them to the jobs.
> Is it possible (and how can I do that) to pass the env content to each job ?
>
> The best would be to have a syntax such as :
> parallel(file:"/path/to/propfilename",
> (
> // job 1, 2 and 3 will be scheduled in parallel. { build("job1") },
> { build("job2") },
> { build("job3") }
> )
> }}
>
>
>
--
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.
