For now, I'm tackling general stability - we're ok for now, it looks like, thanks to a downgrade and some tweaks to configuration, so I may re-enable new MavenModuleSet jobs, not sure yet. We definitely wouldn't force a move to freestyle projects unless we could smoothly migrate existing jobs while retaining existing functionality, don't worry. I'm also working with other Jenkins core devs to get a better understanding of exactly where the MavenModuleSets are causing problems to see if they can be addressed individually, but it's worth reading Stephen Connolly's thoughts on the problems of the MavenModuleSet as a way of executing Maven, not just in terms of its architectural flaws in the master - http://javaadventure.blogspot.com/2013/11/jenkins-maven-job-type-considered-evil.html
A.
