[JIRA] (JENKINS-40070) ${env.GLOBALSETTINGSNAME} invalid out of node context

[dotheb...@citadel.org (JIRA)]

Title: Message Title

Wilfried Goesgens created an issue   Jenkins / JENKINS-40070 ${env.GLOBALSETTINGSNAME} invalid out of node context Issue Type: Bug Assignee: Unassigned Components: pipeline Created: 2016/Nov/28 12:07 PM Priority: Minor Reporter: Wilfried Goesgens Configuring a global variable via Manage Jenkins->Configure System->[Global properties]Name=TEST, Value=test and trying to use it inside a pipeline script like that: Unable to find source-code formatter for language: code. Available languages are: actionscript, html, java, _javascript_, none, sql, xhtml, xml echo( "[ ${env.TEST} ]") stage("test") { echo( "[ ${env.TEST}} ]") node("master") { echo( "[ ${env.TEST}} ]") ... Will output: Unable to find source-code formatter for language: code. Available languages are: actionscript, html, java, _javascript_, none, sql, xhtml, xml [Pipeline] echo [ null ] [Pipeline] stage [Pipeline] { (test) [Pipeline] echo [ null ] [Pipeline] node Running on master in /var/lib/jenkins/workspace/test [Pipeline] { [Pipeline] echo [ test ] The expectation would be that its either available in the global context too or error out to fail visually. Since one may want to use Global properties to build parameters for sub-build jobs having to wrap them in a node(){} will waste worker resources, right? Thus I would like to get global properties to become available outside of nodes too. 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.