Hi, Upstream Jenkins disk always get filled up and I want to reduce the amount of builds to keep from 40 to 30 or even 20 and the amount of archived artifacts to keep from 20 to 15 or even 10. Is that OK by you? Thanks Gil _______________________________________________ Devel mailing list Devel(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/devel

On Wed, Apr 13, 2016 at 12:42 PM, Eyal Edri <eedri(a)redhat.com&gt; wrote: > +1 from me. > > We are in the process of migration to the new jenkins [2], Actually some > of the jobs already migrated (node/lago), > So we will be able to increase history back to higher levels once we > finish the migration. > > I think on some projects we reduced it to 20 already, which projects > still use 40? > Note that the request here is to reduce from 20 to 10 the archived builds. This means that you probably won't be able anymore to inspect logs for a failing job unless it's a job triggered just once every 2 hours. I think that 20 is already a low number enough at least for most of the jobs. I'm ok with reducing the archiving for jobs running once a day. > > e. > > On Mon, Apr 11, 2016 at 5:01 PM, Gil Shinar <gshinar(a)redhat.com&gt; wrote: > >> Hi, >> >> Upstream Jenkins disk always get filled up and I want to reduce the >> amount of builds to keep from 40 to 30 or even 20 and the amount of >> archived artifacts to keep from 20 to 15 or even 10. >> >> Is that OK by you? >> >> Thanks >> Gil >> >> _______________________________________________ >> Devel mailing list >> Devel(a)ovirt.org >> http://lists.ovirt.org/mailman/listinfo/devel >> > > > > -- > Eyal Edri > Associate Manager > RHEV DevOps > EMEA ENG Virtualization R&D > Red Hat Israel > > phone: +972-9-7692018 > irc: eedri (on #tlv #rhev-dev #rhev-integ) > > _______________________________________________ > Devel mailing list > Devel(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/devel > -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com