Hey All, Jenkins is up and running now. It is running only MASTER tests so far, but I'm planning to add the rest of the branches + Java8 next week. http://ec2-54-177-240-2.us-west-1.compute.amazonaws.com/
For people used to know Jenkins, now the PreCommit-Admin is executed from ' builds.apache.org'. This is the job that detects which patches need to be executed, and it then calls the PreCommit-HIVE-Build job, that it then calls the MASTER-Build job for ptest on our own Hive jenkins server. Please let me know if there are issues with the environment so that I can fix it. BTW, I would like to have a better CI system for Hive where we can have the following: - Build pipeline that gives build/test feedback as soon as one stage fails, and to speed up queue waiting times (this requires many changes on ptest code) - Keep all jobs and stages in our Hive source code to quickly recreate a CI environment - Integrate Git PR into the pipeline (if we plan to move from review board to PR in the future) We can either try TravisCI or the new Jenkins 2.0. But, I'd like to ask the community to help doing some investigation, experiments and provide ideas about what's a better approach. Maybe rewriting part of our ptest code. I've been doing experiments with Docker in parallel and Starcluster, but I have other Hive development to do, so I think we should put the community effort here as well. If there're people interested, I can start sharing some information about it. - Sergio On Fri, Apr 22, 2016 at 1:37 AM, Dmitry Tolpeko <dmtolp...@gmail.com> wrote: > Also should we re-submit patches? > > Thanks, > Dmitry > > On Fri, Apr 22, 2016 at 6:47 AM, Li, Rui <rui...@intel.com> wrote: > > > Shall we hold on the commits before Jenkins is back? > > > > Cheers, > > Rui Li > > > > -----Original Message----- > > From: Sergio Pena [mailto:sergio.p...@cloudera.com] > > Sent: Friday, April 22, 2016 12:48 AM > > To: Thejas Nair > > Cc: dev; sze...@apache.org > > Subject: Re: Cannot connect Precommit Jenkins job > > > > Hey Thejas, > > > > The Jenkins server stopped working for other reasons unrelated to the > > patches committed, and the Jenkins jobs were lost. > > I'm still working on it, and I almost have it ready to continue testing > > the master branch. Just a couple of tests more, and I'll release it to > the > > public. I expect to have it ready by tomorrow. > > > > On Wed, Apr 20, 2016 at 6:56 PM, Thejas Nair <thejas.n...@gmail.com> > > wrote: > > > > > Hi Sergio, > > > I saw that once of the recent commits I reviewed was causing issues, > > > sorry about that. > > > Are there other issues to be resolved to get it working ? Any estimate > > > of how much time it might take to get it running again ? > > > Thanks again for your help! > > > > > > -Thejas > > > > > > > > > On Tue, Apr 19, 2016 at 2:09 PM, Sergio Pena > > > <sergio.p...@cloudera.com> > > > wrote: > > > > Hey Thejas, > > > > > > > > We have some internal issues with the Jenkins server. > > > > I'm working on the configuration. > > > > > > > > On Tue, Apr 19, 2016 at 3:35 PM, Thejas Nair <thejas.n...@gmail.com> > > > wrote: > > > >> > > > >> Hi Szehon, Sergio, > > > >> Do you know what is going on with it ? Does it need a restart ? > > > >> Thanks for your help! > > > >> Thejas > > > >> > > > >> > > > >> On Mon, Apr 18, 2016 at 1:58 PM, Wei Zheng <wzh...@hortonworks.com> > > > wrote: > > > >> > Which one is down? AWS or our job? > > > >> > > > > >> > > > > http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommi > > > t-HIVE-TRUNK-Build/ > > > >> > > > > >> > Thanks, > > > >> > Wei > > > > > > > > > > > > > >
