On 10/23/2013 11:26 AM, Andy Doan 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: > > 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 Whichever way we go with this I will still need a listing of all of the jobs to be archived (on the private jenkins instances) as I will need to remove them from the public jenkins instance as well.
~w -- Mailing list: https://launchpad.net/~canonical-ci-engineering Post to : [email protected] Unsubscribe : https://launchpad.net/~canonical-ci-engineering More help : https://help.launchpad.net/ListHelp
