[Box-Admins] Proposed week-long shutdown of Jenkins

[David T. Lewis]

What problem are we trying to solve here?

If there are Jenkins jobs that cause problems, and if those problems
cannot be addressed right away, then the appropriate thing to do is
disable them using the normal Jenkins console. If an explanation is
needed, just update the job description to say what is going on.

A little bit of updating of the Jenkins job descriptions would do no harm
in any case. Sort of like a class comment: "I am a Jenkins job that tests
the FreebleBaz package. If I stop working, please contact
bilbo at baggins.org".

:)

Dave

> Ken and I have been thinking of shutting down Jenkins (OK, it was my idea)
> for a week after 4.5 is released. The aim is to address hanging issues.
>
> A week is a long time from a technical point of view, but it allows people
> using it to take a break. Mainly we're thinking of Frank here.
> We're thinking of upgrades, disk usage, necessary and un-necessary builds
> (if there are any). Basically stopping that world for a week.
>
> What do you think, Frank? If you are opposed, then we'll chuck this idea.
>
> Chris