Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-42360

Globals not accessible in Declarative Pipeline outside script directive

      See https://github.com/jenkins-infra/jenkins.io/pull/611

      Basically, it was a design decision to not allow any form of thing.method() in Declarative. This was needed to support validation.

      It is possible to circumvent this in several ways and there are bugs that might address this, but it is a hard problem.

          [JENKINS-42360] Globals not accessible in Declarative Pipeline outside script directive

          Liam Newman created issue -
          Liam Newman made changes -
          Summary Original: Globals not accessible in Declarative Pipeline. New: Globals not accessible in Declarative Pipeline outside script directive
          Liam Newman made changes -
          Description New: See https://github.com/jenkins-infra/jenkins.io/pull/611

          I need go back over this to see what the actually behavior is.
          Liam Newman made changes -
          Remote Link New: This issue links to "PR 611 (Web Link)" [ 15497 ]
          Liam Newman made changes -
          Link New: This issue relates to WEBSITE-321 [ WEBSITE-321 ]
          Liam Newman made changes -
          Description Original: See https://github.com/jenkins-infra/jenkins.io/pull/611

          I need go back over this to see what the actually behavior is.
          New: See https://github.com/jenkins-infra/jenkins.io/pull/611

          I need go back over this to see what the actually behavior is. Steps from shared libraries work, but Globals (defined using class) are not. Not sure about what happens without a class.


          Liam Newman made changes -
          Link New: This issue relates to JENKINS-37011 [ JENKINS-37011 ]
          Liam Newman made changes -
          Description Original: See https://github.com/jenkins-infra/jenkins.io/pull/611

          I need go back over this to see what the actually behavior is. Steps from shared libraries work, but Globals (defined using class) are not. Not sure about what happens without a class.


          New: See https://github.com/jenkins-infra/jenkins.io/pull/611

          Basically, it was a design decision to not allow any form of {{thing.method()}} in Declarative. It is possible to circumvent this in several ways, and there are bugs that might address this.
          Liam Newman made changes -
          Description Original: See https://github.com/jenkins-infra/jenkins.io/pull/611

          Basically, it was a design decision to not allow any form of {{thing.method()}} in Declarative. It is possible to circumvent this in several ways, and there are bugs that might address this.
          New: See https://github.com/jenkins-infra/jenkins.io/pull/611

          Basically, it was a design decision to not allow any form of {{thing.method()}} in Declarative. This was needed to support validation.

          It is possible to circumvent this in several ways and there are bugs that might address this, but it is a hard problem.
          Liam Newman made changes -
          Link New: This issue relates to JENKINS-41335 [ JENKINS-41335 ]
          Andrew Bayer made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]

            abayer Andrew Bayer
            bitwiseman Liam Newman
            Votes:
            2 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated:
              Resolved: