can you post a full example?

I'm seeing this as well, with both WithEnv and WithCredentials (while populating env vars)

Simple example

container('jnlp') {
  withEnv(['MYTOOL_HOME=/usr/local/mytool']) {
    sh 'env'
  }
}

In the output of env, 'MYTOOL_HOME' will not be set.

Jenkins ver. 2.38, Jenkins k8s 0.10

Nevermind it just doesn't show up in env.... it's there using substitution like this

        echo "${env.MYTOOL_HOME}"

runEnv = []
runEnv.add('JAVA_OPTS=-Xmx6g')
runEnv.add('npm_config_registry=http://nexus.default.svc.cluster.local:8081/repository/npm/')
withEnv(runEnv) {
      try {
           sh './gradlew --stacktrace --parallel jenkinsBuild'
      } catch (Exception e) {
           junit allowEmptyResults: true, testResults: '**/build/test-results/**/*.xml'
           step([$class: 'CheckStylePublisher', canComputeNew: false, defaultEncoding: '', healthy: '', pattern: '**/main.xml,**/test.xml', unHealthy: ''])
           throw e
}

Adding a

sh 'printenv'

Shows the env is not populated

P.s it is inside a container which contains JDK 7 & gcloud

 node('JavaPod') {
                container('gcloud-jdk7') {

Following up, can confirm it is a problem with the container step, The first printenv is correctly populated, but the second is not

node('JavaPod') {
    withEnv(runEnv) {
            sh 'printenv'
    }
    container('gcloud-jdk7') {
            withEnv(runEnv) {
                    sh 'printenv'
             } 
}

Can we confirm that this is a bug with the plugin, and not our setup? It requires ugly workarounds in its present state.

It was never meant to work in the first place.

The container block is only meant to be used with the `sh` function or shell based function.

I would add then env variables in the pod definition or if that is not possible I would set them in the `sh` command.

iocanel if that is indeed the case, then the README should be updated to state that.