[JIRA] (JENKINS-55587) Env variables not available in pipeline options sections, outside of stages

[luke.lussen...@gmail.com (JIRA)]

Title: Message Title

Luke Lussenden edited a comment on JENKINS-55587   Re: Env variables not available in pipeline options sections, outside of stages I use the options style lock to wrap a few stages in a large pipeline and I have the same problem.  Even though the lock is deep within the pipeline, it seems the options are per-computed before the run and the ENV variables are not yet injected.   For my use case - I would really like to use the `GIT_URL` provided by the multibranch pipeline project as the source of my lock.  I don't mind multiple branches building at once, but there is a section they can't be in at the same time if they are on the same repo. ``` {code: groovy } stages {      stage('do stuff 1'){}      stage('do stuff 2'){}      stage('locked set'){         stages {             options \ { lock(resource: "${GIT_URL}") }             stage('first action set') \ { }             stage('second action set') \ { }         }     }     stage('do final stuff'){} } {code} ``` If you have a parameterized build - I believe parameters are available to the options blocks - but not environment variables. Add Comment   This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196752.1547507207000.988.1583530680216%40Atlassian.JIRA.