New warning after updating to 2.492.2

Using Jenkins Ask a question
1

After updating to Jenkins 2.492.2 I’ve started to see warnings in my pipeline console similar to, “Did you forget the def keyword? WorkflowScript seems to be setting a field named {variableName} (to a value of type Integer) which could lead to memory leaks or other issues..”. Nothing has changed in my pipeline script, and as far as I know I’m not doing anything unusual in the pipeline. It looks similar to…

MyGlobalVariable = 69

pipeline {
  agent {
    label 'master'
  }
  stages {
    stage('First Stage') {
      agent { label 'master }
      steps {
        script {
          println("My Variable = ${MyGlobalVariable}")
        }
      }
    }
  }
}

I’ve tried putting ‘def’ before the global variable, but that causes an error when I try to access the variable (groovy.lang.MissingPropertyException: No such property).

Why am I seeing this warning after upgrading, and how can I resolve it?

1 Like
2

I also see the same issue. Any help would be appreciated.

3

See jenkins - How to use environment variables in a groovy function using a Jenkinsfile - Stack Overflow

So basically this should work without a warning:

import groovy.transform.Field

@Field def MyGlobalVariable = 69

pipeline {
  agent {
    label 'master'
  }
  stages {
    stage('First Stage') {
      steps {
        script {
          println("My Variable = ${MyGlobalVariable}")
        }
      }
    }
  }
}
4

Thank you that fixed it.

5

Is there any way to continue without using the word def? I’ve tried to downgrade the pipeline: groovy plugin but I still get the same error.

6

This solution had no effect on the issue in my environment

7

That probably means you have a different problem and your problem needs a different solution. Create a new topic that shows your problem (preferably simplified) and let’s see if others can help