Re: Overriding default Multibranch Pipeline job parameters defined in a Jenkinsfile

Hi, With the declarative pipeline syntax one of the following options might help: 1) Since you already define parameters in the Jenkinsfile

Re: Overriding default Multibranch Pipeline job parameters defined in a Jenkinsfile

I was dealing with similar issue today and only place that I could use to store config was credentials secret text. I stored config as a map and in pipeline, within withCredentials block, I used Eval statement to convert it to proper map, so I could use current branch name as a key to get value.

Re: Overriding default Multibranch Pipeline job parameters defined in a Jenkinsfile

Unfortunately, no. I suppose one solution would be to remove environment specific stuff from the build phase and specify environment specific settings when running the application. May not be a viable solution for you though. On Wednesday, 4 January 2017 12:03:43 UTC+1, Hans Kristian Flaatten w

Re: Overriding default Multibranch Pipeline job parameters defined in a Jenkinsfile

I have the exact same problem! Did you ever find a solution or workaround, Sebastian? On Monday, June 13, 2016 at 4:37:50 PM UTC+2, Sebastian Nowicki wrote: > > Hi, > > I have create a parameterised Multibranch Pipeline job, defining the > parameters and their defaults in a Jenkinsfile inside th

Overriding default Multibranch Pipeline job parameters defined in a Jenkinsfile

Hi, I have create a parameterised Multibranch Pipeline job, defining the parameters and their defaults in a Jenkinsfile inside the repository being built. The job will be built on multiple environments, with separate Jenkins deployments. The defaults set in the Jenkinsfile are production value