loading...

re: Jenkins Pipelines and their dirty secrets 2. VIEW POST

FULL DISCUSSION
 

I was hopeing for a strategy to make it easy to re-run a parameterized job, but to have the last values populated in the defaults, but obviously only when run interactively. Is there a mechanic for doing this using "storage" that get persisted across runs, can I store data by pushing stuff into the properties/props collection? Like at the end of a job I could write these "last used" values back into the job?

code of conduct - report abuse