-
New Feature
-
Resolution: Unresolved
-
Major
-
None
Sometimes it is desirable for a Pipeline script to save and retrieve some state (data) which is persisted across builds.
Possibly could be supported using a plugin which defined a Map-valued global variable made accessible to every Pipeline script which would serialize any values you set to it to a per-job location. (Could even have a variable which held per-master state, though you then need to be careful about access control policies.)
As a workaround, for non-sandboxed jobs, you could use java.io.File calls to read/write a file on the Jenkins master. For example
File f = new File(currentBuild.rawBuild.parent.rootDir, 'my-state')
- is blocking
-
-
- Open
-
- links to
[JENKINS-32982] cross-build state
| Link | New: This issue is blocking JENKINS-27127 [ JENKINS-27127 ] |
| Workflow | Original: JNJira [ 168706 ] | New: JNJira + In-Review [ 183237 ] |
| Component/s | New: pipeline-general [ 21692 ] |
| Component/s | Original: workflow-plugin [ 18820 ] |
| Component/s | New: workflow-basic-steps-plugin [ 21712 ] | |
| Component/s | Original: pipeline [ 21692 ] |
| Summary | Original: Cross-build state | New: Pass environment variables between stages and nodes |
| Summary | Original: Pass environment variables between stages and nodes | New: cross-build state |
| Remote Link | New: This issue links to "CloudBees Internal CD-222 (Web Link)" [ 19087 ] |