Could any PMC grant the access of Jenkins to any of us (committers) so we can proceed it?
On Thu, Feb 23, 2012 at 2:14 AM, Mohammad Islam <[email protected]> wrote: > So this is the conclusions so far: > 1. There should be a nightly build. We need to setup CI for Oozie. > 2. During commit, using Linux for test cases is not a must. but it might > help. > 3. Before any release, everything should be tested in Linux. > > One action Item: Setting up CI. > Is there any volunteer? > > Regards, > Mohammad > > > > > ________________________________ > From: Chris Douglas <[email protected]> > To: "[email protected]" <[email protected]> > Sent: Wednesday, February 22, 2012 9:04 PM > Subject: Re: Feedback requested: Building in Linux/Mac/Doesn't matter > > This looks like a good place to start: > > http://wiki.apache.org/general/Jenkins > > -C > > On Wednesday, February 22, 2012, Alejandro Abdelnur wrote: > > > Thanks Chris, what is the process to get CI (Jenkins I assume) for Oozie? > > > > Alejandro > > > > On Wed, Feb 22, 2012 at 8:34 PM, Chris Douglas <[email protected] > <javascript:;>> > > wrote: > > > > > On Wed, Feb 22, 2012 at 7:53 PM, Santhosh Srinivasan < > [email protected]<javascript:;> > > > > > > wrote: > > > > AFAIK there are no Mac installations of the Hadoop, Pig, Oozie, etc. > > > Given that the cost of catching a failing unit test during release time > > > (given that we don't have CI in Apache) is fairly high. Most of you > must > > > have noticed unit test case failures on the recent release. > > > > > > CI resources are available, if interest drives someone to work on it. > > > What makes a failing unit test expensive during release time? > > > > > > > Use of a Mac (or Windows ;) is a convenience that we can't forego. > What > > > are the best practices in the other Apache projects? > > > > > > In Hadoop, Windows+Cygwin was supported while developers who used it > > > cared to fix those bugs. When they didn't, some unit tests > > > consistently failed on that platform. Most projects either rely on CI > > > or an auditing phase during release. It's not the end of the world if > > > corners of trunk, or any development branch, are broken for awhile. > > > > > > YMMV, but nightly builds are usually sufficient to catch regressions. > > > Does this need a policy? Surely no release would go out if it didn't > > > work on Linux. -C > > > > > > > Santhosh > > > > > > > > -----Original Message----- > > > > From: [email protected] <javascript:;> [mailto: > [email protected]<javascript:;>] > > On Behalf Of > > > Roman Shaposhnik > > > > Sent: Wednesday, February 22, 2012 4:34 PM > > > > To: [email protected] <javascript:;> > > > > Cc: Mohammad Islam > > > > Subject: Re: Feedback requested: Building in Linux/Mac/Doesn't matter > > > > > > > > On Wed, Feb 22, 2012 at 4:22 PM, Alejandro Abdelnur < > [email protected]<javascript:;> > > > > > > wrote: > > > >> To run tests on a given platform? No, but if doing hadoop native > > > >> stuff, only linux is supported at the moment. > > > > > > > > I must add to that: there is absolutely a hard requirement for > > > test-patch not failing to build. And that build is a Linux one. > > > > > > > > Thanks, > > > > Roman. > > > > > >
