Accessing Pipeline as Code Saved State
15 views
Skip to first unread message
Jimmy Ray
Oct 12, 2016, 9:31:51 AM10/12/16
to Jenkins Developers
At Jenkins World 2016, I heard a few conversations about the pipeline state saving functionality, and why live objects should not persist outside of functions. There were one or two conversations that proposed how jobs could actually access these "saved states". I never heard any concrete info on how this could done or even if this could be done.
Is this possible? Can jobs access their own saved states? If so how?
-Jimmy
Jesse Glick
Oct 12, 2016, 2:32:25 PM10/12/16
to Jenkins Dev
On Wed, Oct 12, 2016 at 9:31 AM, Jimmy Ray <jimmy...@gmail.com> wrote:
> At Jenkins World 2016, I heard a few conversations about the pipeline state
> saving functionality, and why live objects should not persist outside of
> functions. There were one or two conversations that proposed how jobs could
> actually access these "saved states". I never heard any concrete info on
> how this could done or even if this could be done.
I do not recall participating in any conversation on the topic, and I
> At Jenkins World 2016, I heard a few conversations about the pipeline state
> saving functionality, and why live objects should not persist outside of
> functions. There were one or two conversations that proposed how jobs could
> actually access these "saved states". I never heard any concrete info on
> how this could done or even if this could be done.
am not really sure what would be meant by this or what the purpose
would be.
For plugin developers, there is a `Pickle` API which allows otherwise
“live” objects to be persisted.
Reply all
Reply to author
Forward
0 new messages