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 wrote: > > 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 the repository being >> built. >> >> The job will be built on multiple environments, with separate Jenkins >> deployments. The defaults set in the Jenkinsfile are production values, but >> I'd like to be able to set different values globally in the other >> deployments. Is there any way to override the default value globally for >> the whole job? >> >> I've found the Environment Injector >> <https://wiki.jenkins-ci.org/display/JENKINS/EnvInject+Plugin> plugin, >> but it doesn't seem like it's possible to customize a job which uses a >> Jenkinsfile. >> > -- 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 jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/7a5b283c-ad33-428b-8aa0-dbb861c62bdc%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
