Good question!
> … I believe this means that only runtime
> persistence for running Pipelines has changed, and none of the previously
> existing on-disk state for Pipeline Runs will change. Would that be correct?
Yes, the format of build data for completed Pipelines is unchanged, so you’ll
still be able to access old Pipelines inside of Jenkins after the upgrade.
To get into the details a bit, the file whose format has changed is `program.dat`,
which stores the Pipeline program and is used to maintain control flow across
restarts. If you don’t stop a Pipeline during the restart, then after restarting,
Jenkins won’t be able to deserialize `program.dat` back into the original
Pipeline program, so the build will fail. Once a Pipeline completes,
`program.dat` is deleted, hence the recommendation to wait for running
Pipelines to complete or to stop them manually if having running Pipelines fail
after the restart would be a problem for your Jenkins installation.
Hopefully that answers your question, but please let me know if there is
anything else I can clarify in regards to the upgrade. Any suggestions to
improve the changelog warning are also welcome.
Thanks,
Devin
> --
> You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to
jenkinsci-use...@googlegroups.com.
> To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/20190104195952.pucqh6wo27xxb7d2%40grape.brokenco.de.
> For more options, visit
https://groups.google.com/d/optout.