On Thu, Mar 7, 2013 at 12:38 AM, ron minnich <[email protected]> wrote: > I'm not convinced. > > ron > > On Wed, Mar 6, 2013 at 9:48 AM, Paul Menzel > <[email protected]> wrote: >> Dear coreboot folks, >> >> >> Jenkins seems to be configured to delete build logs after a certain >> amount of time. For example #4000 is not there anymore [1]. >> >> I am aware that Jenkins has to build a lot of commits (and their >> iterations). For archival purposes, I’d vote for keeping the logs, if >> possible. For example to find out if certain warnings have existed >> already without having to rebuild locally. >> >> With big hard drives and compression that should be doable, right? >> >> >> Thanks, >> >> Paul >> >> >> [1] http://qa.coreboot.org/job/coreboot-gerrit/4000/ >> >> -- >> coreboot mailing list: [email protected] >> http://www.coreboot.org/mailman/listinfo/coreboot > > -- > coreboot mailing list: [email protected] > http://www.coreboot.org/mailman/listinfo/coreboot
Hello! Ron, he's right. I just checked and it seems that everything including that number is not at home. Perhaps there's a finite limit to how many records the bot can work with? ----- Gregg C Levine [email protected] "This signature fought the Time Wars, time and again." -- coreboot mailing list: [email protected] http://www.coreboot.org/mailman/listinfo/coreboot
