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 <denn...@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-unsubscr...@maven.apache.org > >> For additional commands, e-mail: dev-h...@maven.apache.org > >> > > > > > > -- > > 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 > --------------------------------------------------------- > > 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: aherit...@gmail.com Twitter/Skype : aheritier
