On Sat, Mar 22, 2014 at 3:04 AM, teilo <[email protected]> wrote:
> Hi Les,
>
> Firstly a workspace will never give you true stateless in Jenkins à workspace
> availability is best effort (slave may be unavailable, workspace may be
> deleted to reclaim slave disk space...)
>
> Depending on what state you want to store you should look at writing either
> an extension to the build flow, or a new plugin or a combination of both.
The states I'd want to store are the polling status of the underlying
subversion repository related to the job, and the archived job results
collected from the sub-jobs. Things that you just expect every
jenkins job to provide, and that have nothing to do with slave
availability other than needing them temporarily before you can
archive their artifacts. I don't understand the point of removing
these things and then suggesting a plugin extension just to put them
back.
--
Les Mikesell
[email protected]
--
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
