You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Jason van Zyl <ja...@tesla.io> on 2012/11/26 09:06:31 UTC
Maven Core to Git
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
Re: Maven Core to Git
Posted by Dennis Lundberg <de...@apache.org>.
On 2012-11-26 19:49, Jason van Zyl wrote:
>
> On Nov 26, 2012, at 10:41 AM, Dennis Lundberg <de...@apache.org> wrote:
>
>> On 2012-11-26 15:59, Jason van Zyl wrote:
>>>
>>> On Nov 26, 2012, at 12:47 AM, Kristian Rosenvold <kr...@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-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: dev-help@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-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@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-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven Core to Git
Posted by Jason van Zyl <ja...@tesla.io>.
On Nov 26, 2012, at 10:41 AM, Dennis Lundberg <de...@apache.org> wrote:
> On 2012-11-26 15:59, Jason van Zyl wrote:
>>
>> On Nov 26, 2012, at 12:47 AM, Kristian Rosenvold <kr...@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.
> 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.
>
>>>
>>>
>>> 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-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@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-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@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.)
Re: Maven Core to Git
Posted by Jason van Zyl <ja...@tesla.io>.
Agree. Shit happens, we'll deal with it. For now let's just lock it down to one machine. We can also just setup individual builds on the separate machines. No big deal.
jvz
On 2012-11-26, at 11:18 AM, Kristian Rosenvold <kr...@gmail.com> wrote:
>> 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.
>
> Additionally, there is
> https://issues.jenkins-ci.org/browse/JENKINS-6604 which was fixed in
> remoting
> 4 days ago. According to the issue text it renders the slaves
> "unusable". To which extent that makes the
> remote poller crash out is also unknown. But it's "known" that we have
> a *lot* of 6604 on the nodes,
> especially right after a restart. I am unsure what effect a single
> "bad apple" among the remote nodes
> has and to what extent we would detect it.
>
>
> Reading the jenkins code makes me quite sure that any build that is locked to
> 1 specific node will not encounter any of the network-down issues. I
> don't really understand
> how to get "assignedNode"
> (https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/AbstractProject.java#L354)
> to be non-null but that should stop the random reallocations. I assume we could
> lock a few of the jobs down to given nodes and keep some open while we
> continue to track the problem ?
>
>>
>> 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. 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?
>
> I believe all wagon, surefire and scm have all been released from git,
> so I think we're in the clear on /that/ particular aspect.
>
> Personally I think we should go ahead and convert core too.
>
>
> Kristian
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven Core to Git
Posted by Benson Margulies <bi...@gmail.com>.
On the jenkins question, Why don't all the other Apache projects for
which I'm on the dev list suffer from this?
On the RM question, I don't think it's worth waiting. The core is the
thing we release least often. We've run a release or two on the
components we've already migrated, and whomever runs the first core
release from git can be sure to add notes to the doc.
On Mon, Nov 26, 2012 at 2:44 PM, Stephen Connolly
<st...@gmail.com> wrote:
> Kristian, can you ping me on irc tomorrow and maybe I can put some time
> into sorting the issues out (from the Jenkins side)
>
> On Monday, 26 November 2012, Kristian Rosenvold wrote:
>
>> > 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.
>>
>> Additionally, there is
>> https://issues.jenkins-ci.org/browse/JENKINS-6604 which was fixed in
>> remoting
>> 4 days ago. According to the issue text it renders the slaves
>> "unusable". To which extent that makes the
>> remote poller crash out is also unknown. But it's "known" that we have
>> a *lot* of 6604 on the nodes,
>> especially right after a restart. I am unsure what effect a single
>> "bad apple" among the remote nodes
>> has and to what extent we would detect it.
>>
>>
>> Reading the jenkins code makes me quite sure that any build that is locked
>> to
>> 1 specific node will not encounter any of the network-down issues. I
>> don't really understand
>> how to get "assignedNode"
>> (
>> https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/AbstractProject.java#L354
>> )
>> to be non-null but that should stop the random reallocations. I assume we
>> could
>> lock a few of the jobs down to given nodes and keep some open while we
>> continue to track the problem ?
>>
>> >
>> > 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. 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?
>>
>> I believe all wagon, surefire and scm have all been released from git,
>> so I think we're in the clear on /that/ particular aspect.
>>
>> Personally I think we should go ahead and convert core too.
>>
>>
>> Kristian
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org <javascript:;>
>> For additional commands, e-mail: dev-help@maven.apache.org <javascript:;>
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven Core to Git
Posted by Stephen Connolly <st...@gmail.com>.
Kristian, can you ping me on irc tomorrow and maybe I can put some time
into sorting the issues out (from the Jenkins side)
On Monday, 26 November 2012, Kristian Rosenvold wrote:
> > 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.
>
> Additionally, there is
> https://issues.jenkins-ci.org/browse/JENKINS-6604 which was fixed in
> remoting
> 4 days ago. According to the issue text it renders the slaves
> "unusable". To which extent that makes the
> remote poller crash out is also unknown. But it's "known" that we have
> a *lot* of 6604 on the nodes,
> especially right after a restart. I am unsure what effect a single
> "bad apple" among the remote nodes
> has and to what extent we would detect it.
>
>
> Reading the jenkins code makes me quite sure that any build that is locked
> to
> 1 specific node will not encounter any of the network-down issues. I
> don't really understand
> how to get "assignedNode"
> (
> https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/AbstractProject.java#L354
> )
> to be non-null but that should stop the random reallocations. I assume we
> could
> lock a few of the jobs down to given nodes and keep some open while we
> continue to track the problem ?
>
> >
> > 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. 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?
>
> I believe all wagon, surefire and scm have all been released from git,
> so I think we're in the clear on /that/ particular aspect.
>
> Personally I think we should go ahead and convert core too.
>
>
> Kristian
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org <javascript:;>
> For additional commands, e-mail: dev-help@maven.apache.org <javascript:;>
>
>
Re: Maven Core to Git
Posted by Kristian Rosenvold <kr...@gmail.com>.
https://issues.apache.org/jira/browse/INFRA-5390 has been updated to
keep a separate it repo.
The issue should be handled by infra "real soon now".
Kristian
2012/11/27 Jason van Zyl <ja...@tesla.io>:
> Yes, but Kristian suggested merging core and its ITs and we all agreed initially but now I think it's more trouble than its worth. At least to start.
>
> On Nov 27, 2012, at 10:52 AM, Brian Fox <br...@infinity.nu> wrote:
>
>> Didn't it used to be that way? (separate)
>>
>>
>> On Tue, Nov 27, 2012 at 4:09 AM, Stephen Connolly <
>> stephen.alan.connolly@gmail.com> wrote:
>>
>>> On 27 November 2012 08:41, Olivier Lamy <ol...@apache.org> wrote:
>>>
>>>> 2012/11/27 Brett Porter <br...@apache.org>:
>>>>>
>>>>> On 27/11/2012, at 10:34 AM, Arnaud Héritier <ah...@gmail.com>
>>> wrote:
>>>>>
>>>>>> On Mon, Nov 26, 2012 at 11:20 PM, Jason van Zyl <ja...@tesla.io>
>>> wrote:
>>>>>>
>>>>>>> I'm going to be working on the core for a few weeks. I am not
>>> convinced
>>>>>>> putting the ITs with the core is workable. I've tried it with a few
>>>>>>> scenarios and it's super confusing to me at least.
>>>>>>>
>>>>>>
>>>>>> +1
>>>>>
>>>>> Agree - makes sense to keep them separate as they are often run against
>>>> different versions of Maven.
>>>> +1.
>>>> That will make that a sort of Maven tck.
>>>>
>>>
>>> Which is what it should be IMHO
>>>
>>>
>>>>
>>>>>
>>>>> - Brett
>>>>>
>>>>> --
>>>>> Brett Porter
>>>>> brett@apache.org
>>>>> http://brettporter.wordpress.com/
>>>>> http://au.linkedin.com/in/brettporter
>>>>> http://twitter.com/brettporter
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Olivier Lamy
>>>> Talend: http://coders.talend.com
>>>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>
>>>>
>>>
>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder & CTO, Sonatype
> Founder, Apache Maven
> http://twitter.com/jvanzyl
> ---------------------------------------------------------
>
> What matters is not ideas, but the people who have them. Good people can fix bad ideas, but good ideas can't save bad people.
>
> -- Paul Graham
>
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven Core to Git
Posted by Jason van Zyl <ja...@tesla.io>.
Yes, but Kristian suggested merging core and its ITs and we all agreed initially but now I think it's more trouble than its worth. At least to start.
On Nov 27, 2012, at 10:52 AM, Brian Fox <br...@infinity.nu> wrote:
> Didn't it used to be that way? (separate)
>
>
> On Tue, Nov 27, 2012 at 4:09 AM, Stephen Connolly <
> stephen.alan.connolly@gmail.com> wrote:
>
>> On 27 November 2012 08:41, Olivier Lamy <ol...@apache.org> wrote:
>>
>>> 2012/11/27 Brett Porter <br...@apache.org>:
>>>>
>>>> On 27/11/2012, at 10:34 AM, Arnaud Héritier <ah...@gmail.com>
>> wrote:
>>>>
>>>>> On Mon, Nov 26, 2012 at 11:20 PM, Jason van Zyl <ja...@tesla.io>
>> wrote:
>>>>>
>>>>>> I'm going to be working on the core for a few weeks. I am not
>> convinced
>>>>>> putting the ITs with the core is workable. I've tried it with a few
>>>>>> scenarios and it's super confusing to me at least.
>>>>>>
>>>>>
>>>>> +1
>>>>
>>>> Agree - makes sense to keep them separate as they are often run against
>>> different versions of Maven.
>>> +1.
>>> That will make that a sort of Maven tck.
>>>
>>
>> Which is what it should be IMHO
>>
>>
>>>
>>>>
>>>> - Brett
>>>>
>>>> --
>>>> Brett Porter
>>>> brett@apache.org
>>>> http://brettporter.wordpress.com/
>>>> http://au.linkedin.com/in/brettporter
>>>> http://twitter.com/brettporter
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>
>>>
>>>
>>>
>>> --
>>> Olivier Lamy
>>> Talend: http://coders.talend.com
>>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>>
>>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder & CTO, Sonatype
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------
What matters is not ideas, but the people who have them. Good people can fix bad ideas, but good ideas can't save bad people.
-- Paul Graham
Re: Maven Core to Git
Posted by Brian Fox <br...@infinity.nu>.
Didn't it used to be that way? (separate)
On Tue, Nov 27, 2012 at 4:09 AM, Stephen Connolly <
stephen.alan.connolly@gmail.com> wrote:
> On 27 November 2012 08:41, Olivier Lamy <ol...@apache.org> wrote:
>
> > 2012/11/27 Brett Porter <br...@apache.org>:
> > >
> > > On 27/11/2012, at 10:34 AM, Arnaud Héritier <ah...@gmail.com>
> wrote:
> > >
> > >> On Mon, Nov 26, 2012 at 11:20 PM, Jason van Zyl <ja...@tesla.io>
> wrote:
> > >>
> > >>> I'm going to be working on the core for a few weeks. I am not
> convinced
> > >>> putting the ITs with the core is workable. I've tried it with a few
> > >>> scenarios and it's super confusing to me at least.
> > >>>
> > >>
> > >> +1
> > >
> > > Agree - makes sense to keep them separate as they are often run against
> > different versions of Maven.
> > +1.
> > That will make that a sort of Maven tck.
> >
>
> Which is what it should be IMHO
>
>
> >
> > >
> > > - Brett
> > >
> > > --
> > > Brett Porter
> > > brett@apache.org
> > > http://brettporter.wordpress.com/
> > > http://au.linkedin.com/in/brettporter
> > > http://twitter.com/brettporter
> > >
> > >
> > >
> > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: dev-help@maven.apache.org
> > >
> >
> >
> >
> > --
> > Olivier Lamy
> > Talend: http://coders.talend.com
> > http://twitter.com/olamy | http://linkedin.com/in/olamy
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
> >
>
Re: Maven Core to Git
Posted by Stephen Connolly <st...@gmail.com>.
On 27 November 2012 08:41, Olivier Lamy <ol...@apache.org> wrote:
> 2012/11/27 Brett Porter <br...@apache.org>:
> >
> > On 27/11/2012, at 10:34 AM, Arnaud Héritier <ah...@gmail.com> wrote:
> >
> >> On Mon, Nov 26, 2012 at 11:20 PM, Jason van Zyl <ja...@tesla.io> wrote:
> >>
> >>> I'm going to be working on the core for a few weeks. I am not convinced
> >>> putting the ITs with the core is workable. I've tried it with a few
> >>> scenarios and it's super confusing to me at least.
> >>>
> >>
> >> +1
> >
> > Agree - makes sense to keep them separate as they are often run against
> different versions of Maven.
> +1.
> That will make that a sort of Maven tck.
>
Which is what it should be IMHO
>
> >
> > - Brett
> >
> > --
> > Brett Porter
> > brett@apache.org
> > http://brettporter.wordpress.com/
> > http://au.linkedin.com/in/brettporter
> > http://twitter.com/brettporter
> >
> >
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
>
>
>
> --
> Olivier Lamy
> Talend: http://coders.talend.com
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: Maven Core to Git
Posted by Olivier Lamy <ol...@apache.org>.
2012/11/27 Brett Porter <br...@apache.org>:
>
> On 27/11/2012, at 10:34 AM, Arnaud Héritier <ah...@gmail.com> wrote:
>
>> On Mon, Nov 26, 2012 at 11:20 PM, Jason van Zyl <ja...@tesla.io> wrote:
>>
>>> I'm going to be working on the core for a few weeks. I am not convinced
>>> putting the ITs with the core is workable. I've tried it with a few
>>> scenarios and it's super confusing to me at least.
>>>
>>
>> +1
>
> Agree - makes sense to keep them separate as they are often run against different versions of Maven.
+1.
That will make that a sort of Maven tck.
>
> - Brett
>
> --
> Brett Porter
> brett@apache.org
> http://brettporter.wordpress.com/
> http://au.linkedin.com/in/brettporter
> http://twitter.com/brettporter
>
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven Core to Git
Posted by Brett Porter <br...@apache.org>.
On 27/11/2012, at 10:34 AM, Arnaud Héritier <ah...@gmail.com> wrote:
> On Mon, Nov 26, 2012 at 11:20 PM, Jason van Zyl <ja...@tesla.io> wrote:
>
>> I'm going to be working on the core for a few weeks. I am not convinced
>> putting the ITs with the core is workable. I've tried it with a few
>> scenarios and it's super confusing to me at least.
>>
>
> +1
Agree - makes sense to keep them separate as they are often run against different versions of Maven.
- Brett
--
Brett Porter
brett@apache.org
http://brettporter.wordpress.com/
http://au.linkedin.com/in/brettporter
http://twitter.com/brettporter
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven Core to Git
Posted by Arnaud Héritier <ah...@gmail.com>.
On Mon, Nov 26, 2012 at 11:20 PM, Jason van Zyl <ja...@tesla.io> wrote:
> I'm going to be working on the core for a few weeks. I am not convinced
> putting the ITs with the core is workable. I've tried it with a few
> scenarios and it's super confusing to me at least.
>
+1
>
> If you're going to convert them, can you please keep them as individual
> repositories for now and I'd like to work with you through some use cases
> because I ran into some problems but you may have ways to work around them.
> I would prefer to merge them together later then assume it will work and
> have to undo it.
>
> On Nov 26, 2012, at 1:41 PM, Dennis Lundberg <de...@apache.org> wrote:
>
> > On 2012-11-26 20:18, Kristian Rosenvold wrote:
> >>> 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.
> >>
> >> Additionally, there is
> >> https://issues.jenkins-ci.org/browse/JENKINS-6604 which was fixed in
> >> remoting
> >> 4 days ago. According to the issue text it renders the slaves
> >> "unusable". To which extent that makes the
> >> remote poller crash out is also unknown. But it's "known" that we have
> >> a *lot* of 6604 on the nodes,
> >> especially right after a restart. I am unsure what effect a single
> >> "bad apple" among the remote nodes
> >> has and to what extent we would detect it.
> >>
> >>
> >> Reading the jenkins code makes me quite sure that any build that is
> locked to
> >> 1 specific node will not encounter any of the network-down issues. I
> >> don't really understand
> >> how to get "assignedNode"
> >> (
> https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/AbstractProject.java#L354
> )
> >> to be non-null but that should stop the random reallocations. I assume
> we could
> >> lock a few of the jobs down to given nodes and keep some open while we
> >> continue to track the problem ?
> >>
> >>>
> >>> 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. 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?
> >>
> >> I believe all wagon, surefire and scm have all been released from git,
> >> so I think we're in the clear on /that/ particular aspect.
> >>
> >> Personally I think we should go ahead and convert core too.
> >
> > Thanks Kristian, that's all I wanted to hear. Please go ahead and
> convert.
> >
> > Just remember to document any differences between svn and git along the
> way.
> >
> >>
> >> Kristian
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >> For additional commands, e-mail: dev-help@maven.apache.org
> >>
> >
> >
> > --
> > Dennis Lundberg
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder & CTO, Sonatype
> Founder, Apache Maven
> http://twitter.com/jvanzyl
> ---------------------------------------------------------
>
> The modern conservative is engaged in one of man's oldest exercises in
> moral philosophy; that is,
> the search for a superior moral justification for selfishness.
>
> -- John Kenneth Galbraith
>
>
>
>
>
>
--
-----
Arnaud Héritier
06-89-76-64-24
http://aheritier.net
Mail/GTalk: aheritier@gmail.com
Twitter/Skype : aheritier
Re: Maven Core to Git
Posted by Jason van Zyl <ja...@tesla.io>.
I'm going to be working on the core for a few weeks. I am not convinced putting the ITs with the core is workable. I've tried it with a few scenarios and it's super confusing to me at least.
If you're going to convert them, can you please keep them as individual repositories for now and I'd like to work with you through some use cases because I ran into some problems but you may have ways to work around them. I would prefer to merge them together later then assume it will work and have to undo it.
On Nov 26, 2012, at 1:41 PM, Dennis Lundberg <de...@apache.org> wrote:
> On 2012-11-26 20:18, Kristian Rosenvold wrote:
>>> 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.
>>
>> Additionally, there is
>> https://issues.jenkins-ci.org/browse/JENKINS-6604 which was fixed in
>> remoting
>> 4 days ago. According to the issue text it renders the slaves
>> "unusable". To which extent that makes the
>> remote poller crash out is also unknown. But it's "known" that we have
>> a *lot* of 6604 on the nodes,
>> especially right after a restart. I am unsure what effect a single
>> "bad apple" among the remote nodes
>> has and to what extent we would detect it.
>>
>>
>> Reading the jenkins code makes me quite sure that any build that is locked to
>> 1 specific node will not encounter any of the network-down issues. I
>> don't really understand
>> how to get "assignedNode"
>> (https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/AbstractProject.java#L354)
>> to be non-null but that should stop the random reallocations. I assume we could
>> lock a few of the jobs down to given nodes and keep some open while we
>> continue to track the problem ?
>>
>>>
>>> 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. 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?
>>
>> I believe all wagon, surefire and scm have all been released from git,
>> so I think we're in the clear on /that/ particular aspect.
>>
>> Personally I think we should go ahead and convert core too.
>
> Thanks Kristian, that's all I wanted to hear. Please go ahead and convert.
>
> Just remember to document any differences between svn and git along the way.
>
>>
>> Kristian
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>
>
> --
> Dennis Lundberg
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder & CTO, Sonatype
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------
The modern conservative is engaged in one of man's oldest exercises in moral philosophy; that is,
the search for a superior moral justification for selfishness.
-- John Kenneth Galbraith
Re: Maven Core to Git
Posted by Dennis Lundberg <de...@apache.org>.
On 2012-11-26 20:18, Kristian Rosenvold wrote:
>> 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.
>
> Additionally, there is
> https://issues.jenkins-ci.org/browse/JENKINS-6604 which was fixed in
> remoting
> 4 days ago. According to the issue text it renders the slaves
> "unusable". To which extent that makes the
> remote poller crash out is also unknown. But it's "known" that we have
> a *lot* of 6604 on the nodes,
> especially right after a restart. I am unsure what effect a single
> "bad apple" among the remote nodes
> has and to what extent we would detect it.
>
>
> Reading the jenkins code makes me quite sure that any build that is locked to
> 1 specific node will not encounter any of the network-down issues. I
> don't really understand
> how to get "assignedNode"
> (https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/AbstractProject.java#L354)
> to be non-null but that should stop the random reallocations. I assume we could
> lock a few of the jobs down to given nodes and keep some open while we
> continue to track the problem ?
>
>>
>> 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. 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?
>
> I believe all wagon, surefire and scm have all been released from git,
> so I think we're in the clear on /that/ particular aspect.
>
> Personally I think we should go ahead and convert core too.
Thanks Kristian, that's all I wanted to hear. Please go ahead and convert.
Just remember to document any differences between svn and git along the way.
>
> Kristian
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven Core to Git
Posted by Kristian Rosenvold <kr...@gmail.com>.
> 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.
Additionally, there is
https://issues.jenkins-ci.org/browse/JENKINS-6604 which was fixed in
remoting
4 days ago. According to the issue text it renders the slaves
"unusable". To which extent that makes the
remote poller crash out is also unknown. But it's "known" that we have
a *lot* of 6604 on the nodes,
especially right after a restart. I am unsure what effect a single
"bad apple" among the remote nodes
has and to what extent we would detect it.
Reading the jenkins code makes me quite sure that any build that is locked to
1 specific node will not encounter any of the network-down issues. I
don't really understand
how to get "assignedNode"
(https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/AbstractProject.java#L354)
to be non-null but that should stop the random reallocations. I assume we could
lock a few of the jobs down to given nodes and keep some open while we
continue to track the problem ?
>
> 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. 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?
I believe all wagon, surefire and scm have all been released from git,
so I think we're in the clear on /that/ particular aspect.
Personally I think we should go ahead and convert core too.
Kristian
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven Core to Git
Posted by Dennis Lundberg <de...@apache.org>.
On 2012-11-26 15:59, Jason van Zyl wrote:
>
> On Nov 26, 2012, at 12:47 AM, Kristian Rosenvold <kr...@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.
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. 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?
>>
>>
>> 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-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@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-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven Core to Git
Posted by Jason van Zyl <ja...@tesla.io>.
On Nov 26, 2012, at 12:47 AM, Kristian Rosenvold <kr...@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-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@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
Re: Maven Core to Git
Posted by Kristian Rosenvold <kr...@gmail.com>.
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
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-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org