The failures from today are just test builds. Today also a new Hudson was installed... so please simply wait a few days until it settles.
If Lucid wants their customer to use nightly builds, they could setup ones on their servers for their customers? For us Hudson mostly a test system to check our commits. And clover is part of that. If somebody wants to install a trunk build, they should always svn checkout and build themselves. Then they can even fix to specific rev no and can always reproduce their build. Uwe "Erick Erickson" <[email protected]> schrieb: >I don't know what other issues you're referring to, but please, please, >please do whatever you can to remove "false failures". It's highly >disconcerting to folks we talk to on the message boards to say >"Functionality you need is in the nightly builds and you can use them, >but >just ignore the errors the build reports. Really, it's OK. Trust us". > >Putting on my corporate IT hat I'd have serious reservations about >using >code that looks broken all the time (even if it's "just a build >artifact")... > >Erick > >On Fri, Jan 21, 2011 at 6:59 PM, Steven A Rowe <[email protected]> wrote: > >> Clover causes Hudson nightly builds to fail intermittently. This is >bad, >> because it looks like Lucene/Solr tests are failing when they are >not. But >> Clover is good, so nobody wants to turn it off. >> >> One possible solution (apologies if this has already been suggested): >make >> new nightly Clover-only Hudson builds, and remove Clover from the >existing >> nightly builds. >> >> I think that would address all of the issues, wouldn't it? >> >> Steve >> -- Uwe Schindler H.-H.-Meier-Allee 63, 28213 Bremen http://www.thetaphi.de --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
