-
Bug
-
Resolution: Not A Defect
-
Minor
-
None
-
Jenkins ver. 1.560
The following simple statement always prints null.
out.println build.workspace
This began happening to existing build-flow jobs when recently upgrading to the build-flow plugin to 0.11, and is reproducible when creating new build-flow jobs as well. This functionality is important when the build-flow job is creating artifacts.
- is related to
-
JENKINS-20843 build flow plugin does not properly initialize workspace but supports options (SCM) that require a workspace
-
- Open
-
[JENKINS-22725] build.workspace always null
Link | New: This issue is related to JENKINS-20843 [ JENKINS-20843 ] |
Attachment | New: flyweight.png [ 25761 ] |
Issue Type | Original: Bug [ 1 ] | New: New Feature [ 2 ] |
Issue Type | Original: New Feature [ 2 ] | New: Bug [ 1 ] |
Resolution | New: Not A Defect [ 7 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Description |
Original:
The following simple statement always prints null. {quote} {{out.println build.workspace}} {quote} This began happening to existing build-flow jobs when recently upgrading to Jenkins 1.560, and is reproducible when creating new build-flow jobs as well. This functionality is important when the build-flow job is creating artifacts. |
New:
The following simple statement always prints null. {quote} {{out.println build.workspace}} {quote} This began happening to existing build-flow jobs when recently upgrading to the build-flow plugin to 0.11, and is reproducible when creating new build-flow jobs as well. This functionality is important when the build-flow job is creating artifacts. |
Priority | Original: Major [ 3 ] | New: Minor [ 4 ] |
Workflow | Original: JNJira [ 154837 ] | New: JNJira + In-Review [ 195052 ] |