[JIRA] (JENKINS-35921) Parameterised build in jenkins: Not getting parameters as env variables

[ashish_b...@yahoo.com (JIRA)]

Title: Message Title

Ashish Behl updated an issue   Jenkins / JENKINS-35921 Parameterised build in jenkins: Not getting parameters as env variables Change By: Ashish Behl Jenkins version: 2.6 - 2.9 Host: Debian 8, Linux 63 bit machine, running in VM. ( jenkins installed through system repos and then updated.) Project type: Multi configuration project. Plugins:          a) Build With Parameters: version 1.3          b) Environment Injector Plugin: version 1.92.1          c) Groovy: 1.29 http://stackoverflow.com/questions/37786301/parameterised-build-in-jenkins-not-getting-parameters-as-shell-env-variables Problem: The parameterized build variables are not are not visible (as env variables) in the Execution step "shell script", They used to be visible in the older 1.x jenkins version. *EDIT[2016-22-june]: THESE PARAMETERS ARE VISIBLE AS ENV VARIABLES ON MASTER BUT NOT ON THE SLAVES.* Steps:     Create a parameterized build with a multi configuration project.     Add a parameter to the build (using This project is parameterized-> string parameter, {if that matters} ).     Add a build step "Execute shell" to the job.     Access these parameters in this shell script as env variables.     echo "++++++++++++ building $lib_name ($lib_version) ++++++++++++++" Workaround--> for the time being, I have tried to create a groovy script in "Prepare an environment for the run" section. I created env variables using hardcoded values which are pased to shell script as env vars. def map = ['lib_name':'lib1'] map['lib_version'] = 'master' return map This makes these "Hardcoded" variables visible in jenkins shell script.. Add Comment   This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.