[JIRA] (JENKINS-38021) Accessing unset global variable cause master to hang

[email protected] (JIRA) Wed, 07 Sep 2016 23:30:28 -0700

Title: Message Title

So you confirm that this is current and intended behavior?
Have you reproduced this?

I think this is insane, especially considering the grave consequence (hanging Jenkins master).

If this is indded the case, I feel that there is strong lack of documentation here: https://github.com/jenkinsci/workflow-cps-global-lib-plugin/blob/master/README.md. It should state:

Docs addition

If you access an unset global variable your Jenkins master will hang indefinitely and need to be restarted
This also means you cannot have the name on the implicit field be the same as the name of the global variable if you want to access it in getter, e.g. to have some checks/default value handling:
```
def getSomething() { return this.something ?: 'somethingDefaultValue' }
```
And from JENKINS-34416:
The global variables singletons are not accessible inside shared code (workflowLibs/src/...) unless you explicitly give it as argument. They will see another instance.
Basically, you should think twice before using this pattern.

PS. I updated the title since I'm not actually sure it's a stack overflow error.

Add Comment

This message was sent by Atlassian JIRA

--
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 [email protected].
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-38021) Accessing unset global variable cause master to hang

Reply via email to