Pass in a parameter/property specified by Jenkins job, not user

[Adam Hardy]

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

[Qiang]

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} ?



[Adam Hardy]

I can't check until I get in on Tuesday but this is a multi-branch pipeline job.

Won't env.JOB_NAME either be the approximately the name of the repo so I know
which app it builds, or the name of the branch in that repo?

If it's the former, I guess I could suffix the name with the environment and
then parse it in the script, but that's not really something I'd like.

[Qiang Ma]

Hmm, JOB_NAME would be auto generated based on the branch name.

User input would make the job pause, so that doesn't seem a good option , either.

Then what else can be different to make the same job performing different deployment?  Branch name? 

--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/4jayfI5ijBQ/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/74a0e435-3ac7-e14e-0d0b-7858080a3de8%40cyberspaceroad.com.
For more options, visit https://groups.google.com/d/optout.

--

Regards,
Qiang

[Adam Hardy]

Yes, exactly, I don't think pausing the job to get the info from the user is a
good way of doing it.

If it isn't possible to pass an extra parameter/property from the Jenkins UI to
the script on job launch and initialization, then I should move onto a different
approach using some other logical means.

However the "parameterized build" option in the job config dialog gave me hope
that such a non-user-defined parameter was feasible.

Is that incorrect?


Qiang Ma wrote on 26/08/18 15:20:

Hmm, JOB_NAME would be auto generated based on the branch name.

User input would make the job pause, so that doesn't seem a good option , either.

Then what else can be different to make the same job performing different
deployment?  Branch name?


On Sun, Aug 26, 2018 at 7:15 AM Adam Hardy <adam....@cyberspaceroad.com
<mailto:adam....@cyberspaceroad.com>> wrote:

  I can't check until I get in on Tuesday but this is a multi-branch pipeline
job.

  Won't env.JOB_NAME either be the approximately the name of the repo so I know
  which app it builds, or the name of the branch in that repo?

  If it's the former, I guess I could suffix the name with the environment and
  then parse it in the script, but that's not really something I'd like.


  --
  You received this message because you are subscribed to a topic in the
  Google Groups "Jenkins Users" group.
  To unsubscribe from this topic, visit
  https://groups.google.com/d/topic/jenkinsci-users/4jayfI5ijBQ/unsubscribe.
  To unsubscribe from this group and all its topics, send an email to
  jenkinsci-use...@googlegroups.com

  <mailto:jenkinsci-users%2Bunsu...@googlegroups.com>.

  To view this discussion on the web visit
 
https://groups.google.com/d/msgid/jenkinsci-users/74a0e435-3ac7-e14e-0d0b-7858080a3de8%40cyberspaceroad.com.
  For more options, visit https://groups.google.com/d/optout.



--

Regards,
Qiang

--
You received this message because you are subscribed to a topic in the Google
Groups "Jenkins Users" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/jenkinsci-users/4jayfI5ijBQ/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
jenkinsci-use...@googlegroups.com

<mailto:jenkinsci-use...@googlegroups.com>.

To view this discussion on the web visit

https://groups.google.com/d/msgid/jenkinsci-users/CAHf%3Dn4yNObgShHRmO%2B6_c_Zr-jtnKApK-T%3DWLu%2B-cd4s4z3d8g%40mail.gmail.com
<https://groups.google.com/d/msgid/jenkinsci-users/CAHf%3Dn4yNObgShHRmO%2B6_c_Zr-jtnKApK-T%3DWLu%2B-cd4s4z3d8g%40mail.gmail.com?utm_medium=email&utm_source=footer>.

[Adam Hardy]

I think I can use env.JOB_BASE_NAME

Failing that I can give different jobs different script paths, and call other scripts with parameters.