WorkspaceCleanupThread: the workspace thread is disabled by default

The workspace cleanup feature should be off by default. It creates a lot of FUD(fear, uncertainty and doubt) when Jenkins starts falling over for no apparant reason after having worked smoothly for months.

With this change, the bug below can be closed because users who don't want this won't be hurt by this feature.

https://issues.jenkins-ci.org/browse/JENKINS-9436
To change the name was intentional. The current behaviour breaks a lot of
Jenkins deployments.

I don't think there is a way to find out, but I'm convinced that if you
could check you'd find that with this you'd fix many more deployments than
you'd break.

On Wed, Dec 3, 2014 at 11:37 AM, Oliver Gondža <notifications@github.com>
wrote:

> In core/src/main/java/hudson/model/WorkspaceCleanupThread.java:
>
> >       */
> > -    public static final boolean disabled = Boolean.getBoolean(WorkspaceCleanupThread.class.getName()+".disabled");
> > +    public static final boolean enabled = Boolean.getBoolean(WorkspaceCleanupThread.class.getName()+".enabled");
>
> Changing the name of the property is going to break existing deployments
> that use it. This change is about changing its default value.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/jenkinsci/jenkins/pull/1478/files#r21223026>.
>



-- 
Øyvind Harboe - Can Zylin Consulting help on your project?
http://www.zylin.com/