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 <[email protected]> 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 > [email protected]. > 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 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/CAHf%3Dn4yNObgShHRmO%2B6_c_Zr-jtnKApK-T%3DWLu%2B-cd4s4z3d8g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
