-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 03/20/2012 08:22 AM, Eyal Edri wrote:
> If
jenkins.ovirt.org will have access to the other servers, we
> might be able to add system jobs that deleted old files and such,
That's an interesting idea. Is that a good way to handle this sort of
thing? Akin to the way Puppet or Chef handle configurations?
> i do it downstream to delete old files from multiple dirs on
> jenkins slaves.
>
> running a cmd like: 'sudo find . -type f -mtime +${days_to_keep}
> |grep -v ^\.$| sudo xargs rm -rf'
OK, I just put that in a small shell script (below) that I put in
root's crontab to run daily.
I know things continue to be a bit hacky. Jason Brooks and I have been
having discussions about how we can make it easier and more scalable
to spin up project infrastructure, as this piecemeal approach is
feeling organically cobbled-together instead of following a good plan.
Maybe organic is fine, but it would help if we could just grab what we
needed, as we needed it (planet? check. jenkins? check. etc.) without
having to worry about all the infrastructure around it. To that end,
Jason has been spinning up services using OpenShift quickstarts.
we started with openshift for jenkins:
1. it still needs a few features to allow it to work for the scale/space
we need.
2. we need slaves which are bare metal for some of the tests.