expanded environment variables in raw oc invocation about jenkins-client-plugin HOT 3 CLOSED

Hi @thikade

Per jenkinsfile references like https://jenkins.io/doc/book/pipeline/jenkinsfile/#working-with-the-environment
and
https://github.com/jenkinsci/pipeline-plugin/blob/master/TUTORIAL.md#managing-the-environment
You have to use the env step, and syntax like "$env.VARNAME" or "${env.VARNAME}"
Note: the double quotation marks are important and required. Can't use single quotes.

As an example, I have the build config "frontend" created in my environment. The following simple Jenkins files work, env.BCNAME is resolved to "frontend".

openshift.withCluster() {
    env.BCNAME = 'frontend'
    echo "GGM ${env.BCNAME}"
    openshift.raw('start-build', "${env.BCNAME}")
}

and

openshift.withCluster() {
    env.BCNAME = 'frontend'
    echo "GGM ${env.BCNAME}"
    openshift.raw('start-build', "$env.BCNAME")
}

from jenkins-client-plugin.

Hi @gabemontero
Thanks a lot for the clarification and examples!

from jenkins-client-plugin.

from jenkins-client-plugin.