[JIRA] (JENKINS-41953) printlns in shared library vars classes are ignored

[davidmichaelk...@gmail.com (JIRA)]

Title: Message Title

David Karr commented on JENKINS-41953   Re: printlns in shared library vars classes are ignored From what I can see, using "echo" or "println" behaves exactly the same way, in a class structure that allows executing them. If anyone has a similar original structure and finds this bug report, the key is that defining a "class" (using the "class" keyword) in "vars" (as opposed to "src") will have this limitation, and it seems, others. This is resolved by making each of the "functional" methods (instance variables are next step) standalone methods in the file. For each instance variable that you need for storing state, you don't actually define an instance variable, you just define "setFoo" and "getFoo" methods, which reference a "foo" variable, like this: def setFoo(value) { foo = value } def getFoo() { return foo } The only annoyance with this is that it seems to cause problems if you try to "get" (or reference) "foo" somewhere before you set it. In my testing, this causes the Jenkins job to hang forever. For now, I have to do things like this if I'm going to reference a variable that might not be set yet: if (binding.variables.containsKey("foo")) { .. } There may be a better way to do this, but I haven't found it yet. In your methods, you should be able to execute steps ("echo" and "println" appear to be synonyms, from my testing). Add Comment   This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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. For more options, visit https://groups.google.com/d/optout.