VFloyd (2015-07-16 16:21):
Morning,
Jumping straight to the point - we have jobs in our Jenkins instance
that have not run in two years (successfully or unsuccessfully). We
have jobs that people set up months ago and have never run. I have
sent e-mails, made visits to peoples desks, made calls all trying to
get people to take care of their jobs and I still have them out there.
I started disabling anything that hadn't run successfully in 12
months. My boss says I am wrong for doing this. I am also wrong for
wanting to shelve or just put these job in a zip file.
I have better things to do. Can anyone give me a for or against
leaving abandoned jobs in Jenkins?
If you remove the job it is lost. That's obviously the main problem of
just deleting jobs. The problem is that not only it's configuration is
lost, but also it's test history and release history (unless you have a
copy of it elsewhere)...
I usually follow this schema:
1. Disable job.
2. If after some time (week, month) nobody cared, then I move the
folder from `jenkins-data/jobs` to `jenkins-data-old/jobs`. That way
it is no longer visible in Jenkins. It's no longer in jenkins-data
backups either.
3. If we start running low on space I remove jobs from `jenkins-data-old`.
At a very least I would just keep a backup of `config.xml` of all jobs.
We have them in SVN so that I don't have to worry too much about
deleting things.
Regards,
Nux.
--
You received this message because you are subscribed to the Google Groups "Jenkins
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/55B20DDD.1040308%40mol.com.pl.
For more options, visit https://groups.google.com/d/optout.
