On Nov 26, 2012, at 12:47 AM, Kristian Rosenvold <kristian.rosenv...@gmail.com> wrote:
> The problem is the asf builds running too often, and sometimes far too > often and hence spamming the mailing lists substantially. Some of it > has been solved, but there are still a few issues remaniing: > > > As far as I can see there are two aspects of the issue: > > 1. A configuration error (or any kind of git corruption/inconsistency) > on any of the git nodes would lead to the jenkins build running > non-stop, generating mass amounts of spam on the notifications mailing > lists. This issue has been solved as far as I can see; both by fixing > the git configuration issue and by patching jenkins to fix the issue. > This was https://issues.jenkins-ci.org/browse/JENKINS-15803. > > 2. There is a second issue where any kind of intermittent disconnect > between the main jenkins instance and its node will trigger a rebuild > because the master does not distinguish between a node being > blank/reconfigured and simply unavaliable at the moment. > > This is basically happening by "workspaceOffline" returning "true" in > https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/AbstractProject.java#L1437 > > I've been meaning to get Olivier to add logging in this code to find > out what is actually happening. It seems to > me like every single glitch in the asf network is causing rebuilds. > And it would appear to be a quite unstable network So in practical terms it all needs to be released, and the servers all updated? Can we just turn off the remote nodes for the time being and just run 1.5/1.6/1.7 on the Ubuntu node? Is that a valid work around? I would prefer to do that in the short term because getting this all this working doesn't seem like it's going to happen very quickly. > > > Kristian > > > 2012/11/26 Jason van Zyl <ja...@tesla.io>: >> Kristian/Olivier, >> >> What exactly is the issue with switching over the core to Git? I only know >> vaguely what the reasoning is because I happened to wander into IRC one day. >> I also see the Jenkins issue[1] referred to in the Infra issue[2] about the >> conversion but it's not clear what's happening there or if it will be fixed >> anytime soon. What exactly is the problem? And why doesn't this behaviour >> exhibit itself in some of the other Git repos we have being built under >> Jenkins? I see tons of other projects using Git and Jenkins so can we >> workaround anything specific we're doing? >> >> [1]: https://issues.jenkins-ci.org/browse/JENKINS-15803 >> [2]: https://issues.apache.org/jira/browse/INFRA-5390 >> >> Thanks, >> >> Jason >> >> ---------------------------------------------------------- >> Jason van Zyl >> Founder & CTO, Sonatype >> Founder, Apache Maven >> http://twitter.com/jvanzyl >> --------------------------------------------------------- >> >> You are never dedicated to something you have complete confidence in. >> No one is fanatically shouting that the sun is going to rise tomorrow. >> They know it is going to rise tomorrow. When people are fanatically >> dedicated to political or religious faiths or any other kind of >> dogmas or goals, it's always because these dogmas or >> goals are in doubt. >> >> -- Robert Pirzig, Zen and the Art of Motorcycle Maintenance >> >> >> >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > Thanks, Jason ---------------------------------------------------------- Jason van Zyl Founder & CTO, Sonatype Founder, Apache Maven http://twitter.com/jvanzyl --------------------------------------------------------- A party which is not afraid of letting culture, business, and welfare go to ruin completely can be omnipotent for a while. -- Jakob Burckhardt
