On Fri, Dec 30, 2011 at 4:45 PM, Andreas Veithen <andreas.veit...@gmail.com> wrote: > In our case, switching to Maven 2.2.1 is a valid workaround, so we > don't really care. > > On the other hand, I guess that many people are annoyed by the issues > that pop up after upgrading to a new Jenkins release (this seems to be > a somewhat recurring issue at the ASF). Therefore it may be a good > idea to install a SNAPSHOT and check for other issues that we may > identify (and if necessary repeat that in several iterations), so that > we eventually get a stable release that works well at the ASF and that > we can keep for a couple of months. WDYT?
That was what we did with the former release. We ran that for like two months or so, but eventually problems like that with StreamCorruptedException creeps up. I guess that's the curse of having a large installation with many different types of builds. /niklas
