canonical-ci-engineering team mailing list archive

[Paul Larson <paul.larson@xxxxxxxxxxxxx>]

I don't see any reason to keep them, and archiving/removing them would
probably be good for the overall health of jenkins. Larry, is there a best
practice for doing this? I would think just backup the job directories,
remove them, and restart jenkins? We could, of course, remove them through
the jenkins api also, but rm/restart may be quite a bit faster.



On Tue, Oct 22, 2013 at 5:57 PM, Evan Dandrea <evan.dandrea@xxxxxxxxxxxxx>wrote:

> Hi everyone,
>
> Do we need to keep around the Jenkins jobs for older releases,
> specifically anything that's not precise or trusty?
>
> For the jobs that we are keeping around, are these used for SRU
> testing? If not, what are they being used for?
>
> Thanks!
>
> --
> Mailing list: https://launchpad.net/~canonical-ci-engineering
> Post to     : canonical-ci-engineering@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~canonical-ci-engineering
> More help   : https://help.launchpad.net/ListHelp
>