Skip to content

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

@jenkins-infra-bot

Description

@jenkins-infra-bot

See jenkins-infra/jenkins.io#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.


Originally reported by bitwiseman, imported from: Globals not accessible in Declarative Pipeline outside script directive
  • assignee: abayer
  • status: Closed
  • priority: Major
  • component(s): pipeline-model-definition-plugin
  • resolution: Won't Fix
  • resolved: 2017-07-06T12:16:18+00:00
  • votes: 2
  • watchers: 9
  • imported: 2025-12-06
Raw content of original issue

See jenkins-infra/jenkins.io#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.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions