On 2012-11-26 19:49, Jason van Zyl wrote: > > On Nov 26, 2012, at 10:41 AM, Dennis Lundberg <denn...@apache.org> wrote: > >> On 2012-11-26 15:59, Jason van Zyl wrote: >>> >>> 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? >> >> There is also >> https://issues.jenkins-ci.org/browse/JENKINS-15367 >> which went into Jenkins 1.492 that was released yesterday, that may or >> may not be a factor in this depending who you talk to. >> >>> 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. >> >> Which ubuntu node would that be? There are 5 of them and I think they >> are all slaves. > > Just run on one machine for the matrix of JDKs we care about if this prevents > the build explosions. > >> >> Apart from these issues I proposed that we release a couple of our own >> products using git, before we move the core over to git. > > We have already haven't we? Apart from that I've done hundreds of releases > out of Git and it works fine. But for core I will take responsibility if the > buck needs to stop somewhere. I just want to get it moved over and work > around any issues until the problems are solved.
Like I said, I don't know the current status on this. It might very well be that we are there now. >> Just so that we >> have a good grasp of how a Maven release using git is done and get it >> properly documented. I'm not up to date on the progress here though. >> Would those of you that have done such releases please let us know? > > The release plugin works fine with Git. I'm sure it does. But for git beginners like myself who has not done a single release using git, we need a well documented release process for it. >> >>>> >>>> >>>> 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 >>> >>> >>> >>> >>> >>> >> >> >> -- >> Dennis Lundberg >> >> --------------------------------------------------------------------- >> 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 > --------------------------------------------------------- > > Simplex sigillum veri. (Simplicity is the seal of truth.) > > > > > > -- Dennis Lundberg --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
