canonical-ci-engineering team mailing list archive

[Evan Dandrea <evan.dandrea@xxxxxxxxxxxxx>]

On 23 October 2013 08:26, Andy Doan <andy.doan@xxxxxxxxxxxxx> wrote:
> On 10/23/2013 10:13 AM, Paul Larson wrote:
>> 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.
>
> We could probably write a groovy script for jenkins that takes in a list of
> regexes. Then for each job that matches on of the regexs we:

Are we certain that we're not doing SRU testing for these releases?
Is there a regex that will let us find only the jobs for which we're
not doing SRU testing?
Andy or Paul, can you please generate a list of these jobs so that we
can circulate them to Ubuntu Engineering before we delete them?
Is there any other criteria we can apply to a regex to find tests we
no longer need?
Can we generalise this process in some way so we're not accruing a lot
of cruft as we stop supporting releases?

Thanks!