Travis or CloudBees, definitely. But is Travis really equipped for builds like ours? We need many JVMs, really big heaps, and a crapload of CPU time...
- Charlie On Tue, Dec 6, 2011 at 1:43 PM, Nick Sieger <nicksie...@gmail.com> wrote: > Yeah, it's a real pain. I noticed the other day that no builds were running > at all and it was because the /builds mount was out of space. I had to free > up a bunch of space and make some other tweaks as well. > > Travis is looking better all the time. > > /Nick > On Dec 5, 2011, at 11:30 PM, Charles Oliver Nutter wrote: > >> Man, is this ever a painful job. >> >> I've spent most of the day trying to get CI builds green again, and >> the server has been working against me. >> >> Most of the major builds were red...the spec builds, test-all, dist, >> and I think jruby-base as well. In the process of fixing one build I >> uncovered regressions in others, or uncovered bugs that caused more >> builds to go red. Needless to say, I didn't expect to spend 15 hours >> on this. >> >> I think I'm finally closing in on having everything green again, and >> there were a few facts that came out of this I wanted to bring to >> everyone's attention. >> >> * As I posted earlier, I added another test-all build for jruby-1_6. >> It should help keep us honest. >> >> * Ant 1.7.0 is a pain in the ass. It appeared to ignore the JDK we >> started it up with and always launched 'java' with whatever the >> command on PATH was. BUT, it would run that JVM with the runtime you >> started it up with...or something like that. In any case, those nasty >> bizarre VerifyErrors came back. Ultimately I ended up going through >> and explicitly making pretty much all builds use the ant182 install of >> ant, *and* I modified Jenkins to puts that ant install at the front of >> PATH. If I didn't do that, it seemed to keep picking up the >> system-wide emerged "ant" and reverting to the old issues. >> >> * I had to bump up permgen on a couple of the precompiled tests again. >> They're at 512M now. I also added permgen size to the spec runs, which >> might cause them to break on JVMs that don't have a permgen flag. I'll >> cross that bridge shortly. >> >> * I also forced almost all builds to run with Java 5. We've had some >> bad Java 6 code sneak through again recently, and we need to keep the >> builds honest across the board. All builds, unless otherwise >> specified, will run with Java 5. >> >> I'm still in progress, but I'll write again in a while as more builds go >> green. >> >> - Charlie >> >> --------------------------------------------------------------------- >> To unsubscribe from this list, please visit: >> >> http://xircles.codehaus.org/manage_email >> >> > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
