Details
-
Improvement
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Won't Fix
-
None
Description
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.
Attachments
Issue Links
- relates to
-
JENKINS-41335 Allow variables and functions to be defined within pipeline to be used in any stage
-
- Closed
-
-
-
- Resolved
-
- links to
Activity
| Field | Original Value | New Value |
|---|---|---|
| Summary | Globals not accessible in Declarative Pipeline. | Globals not accessible in Declarative Pipeline outside script directive |
| Description |
See https://github.com/jenkins-infra/jenkins.io/pull/611 I need go back over this to see what the actually behavior is. |
| Remote Link | This issue links to "PR 611 (Web Link)" [ 15497 ] |
| Link | This issue relates to WEBSITE-321 [ WEBSITE-321 ] |
| Description |
See https://github.com/jenkins-infra/jenkins.io/pull/611 I need go back over this to see what the actually behavior is. |
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. |
| Link |
This issue relates to |
| Description |
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. |
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. |
| Description |
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. |
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. |
| Link |
This issue relates to |
| Status | Open [ 1 ] | In Progress [ 3 ] |
| Remote Link | This issue links to "PR #127 (better error reporting) (Web Link)" [ 15498 ] |
| Resolution | Won't Fix [ 2 ] | |
| Status | In Progress [ 3 ] | Resolved [ 5 ] |
| Status | Resolved [ 5 ] | Closed [ 6 ] |