Is the only purpose of the parameter/property to differentiate between the
devtest/oat/prod?
If that's the case, can you use ${env.JOB_NAME} ?
On Friday, August 24, 2018 at 10:47:14 AM UTC-5, Adam Hardy wrote:
>
> Hi
>
> I'd like my Jenkins multi-branch and pipeline jobs to pass in a
> pre-defined parameter or property to the build script in the git repo
> specified.
>
> This isn't for user input. I'm trying to improve the capabilities of a
> microservices-oriented CD pipeline I inherited.
>
> I want to set up more or less the same job 3 times for each app / git
> repo: once for devtest, once for oat and once for prod.
>
> I'll use it to extract a set of configuration parameters from a yaml file
> in the repo, which will specify stuff like deployment namespace, app,
> version, docker registry url, credential id etc.
>
> At the moment, I can only see how I can change the git repo details or ask
> the user the input.
>
> Thanks
> Adam
>
>
>
>
--
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/d332622d-7bdd-477e-87de-f1d7fd886f8e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
