jenkinsci / jenkinsci/workflow-basic-steps-plugin
[JENKINS-32982] cross-build state
- Lingua principale
- Java
- Stelle
- 73
- Fork
- 129
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Descrizione
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')
---
Originally reported by
jglick, imported from: cross-build state
jglick
Raw content of original issue
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')
Guida per i contributori
Apri la guida per i contributori
Direzione di ricerca
Iniziare con il componente workflow-basic-steps-plugin e verificare come sono attualmente rappresentate le variabili globali di Pipeline e lo stato dei job. Definire l’ambito della persistenza per job, inclusi serializzazione e controllo degli accessi, e considerare il workaround java.io.File descritto nell’issue per determinare cosa dovrebbe supportare una soluzione completa.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- java
- Ambito
- devops
- Tipo di issue
- Funzionalità
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Stato di attività
- Ferma
- Chiarezza
- Da chiarire
- Idoneità per principianti
- 20/100