canonical-ci-engineering team mailing list archive

[Andy Doan <andy.doan@xxxxxxxxxxxxx>]

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:

  copy to a backup directory
  delete the job

This is probably slow but has 2 nice benefits:

1) easy to test. we could make the script do a dry run the first time

2) eliminates downtime

-andy