hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ted Yu <yuzhih...@gmail.com>
Subject Re: Precommit build (hadoopqa) can now test the patch on branches
Date Fri, 30 Jan 2015 23:36:31 GMT
Good idea.

QE bot can start with the latest patch and search backwards until an
attachment which has been tested is found.

On Fri, Jan 30, 2015 at 11:31 AM, Nick Dimiduk <ndimiduk@gmail.com> wrote:

> Thank you so much Enis!
>
> Rather than ballooning our JIRA count, can we update the QE bot to track
> it's work queue more intelligently?
>
> On Fri, Jan 30, 2015 at 10:47 AM, Enis Söztutar <enis@apache.org> wrote:
>
> > Agreed. Subtasks can be used for this.
> >
> > Enis
> >
> > On Fri, Jan 30, 2015 at 9:10 AM, Andrew Purtell <apurtell@apache.org>
> > wrote:
> >
> > > A practice that might be acceptable, if you have a patch for master and
> > one
> > > or more branches ready to go at once, is attach the patch for master to
> > the
> > > "main" issue, open subtasks for each branch patch, attach the
> respective
> > > branch patches to the subtasks, and set them all to Patch Available
> > state.
> > > Later, committers could commit the patches using the identity of the
> main
> > > issue and resolve it and the subtasks in one shot. Just a thought.
> > >
> > >
> > > On Thu, Jan 29, 2015 at 10:31 PM, Enis Söztutar <enis@apache.org>
> wrote:
> > >
> > > > Devs,
> > > >
> > > > Over at HBASE-12944, we've made some changes so that the Precommit
> > > jenkins
> > > > build (commonly known and loved as hadoopqa) can now test patches on
> > > > branches.
> > > >
> > > > For testing a patch on a branch, you should use the name of the
> branch
> > in
> > > > name of the patch file. For example a patch file named
> > > > "hbase-123-0.98.patch will test the hadoopqa build on top of the 0.98
> > > > branch.
> > > >
> > > > Right now, all active branches, master, branch-1.0, branch-1, 0.98
> and
> > > 0.94
> > > > are supported. If no branch name is found in the patch file, master
> > will
> > > be
> > > > used.
> > > >
> > > > Also keep in mind that hadoopqa only picks up the latest patch from
> an
> > > > issue in "Patch Available" state. This means that you cannot attach 3
> > > > patches at the same time for different branches and expect hadoopqa
> to
> > > > report on all 3. The way to test a patch for master and branch-1 for
> > > > example would be to attach the master patch, wait for the precommit
> > build
> > > > [1] to start for your patch, and then after it started attach the
> > > branch-1
> > > > patch with "branch-1" in the patch file name. There is another job
> > called
> > > > PreCommit-Admin [2] who looks at the jira issues and kicks the
> > precommit
> > > > build every 10 minutes. It means you have to wait at least 10 minutes
> > in
> > > > between (or kick [2] manually if you are a committer).
> > > >
> > > > [1] https://builds.apache.org/job/PreCommit-HBASE-Build/
> > > > [2] https://builds.apache.org/view/All/job/PreCommit-Admin/
> > > >
> > > > Cheers,
> > > > Enis
> > > >
> > >
> > >
> > >
> > > --
> > > Best regards,
> > >
> > >    - Andy
> > >
> > > Problems worthy of attack prove their worth by hitting back. - Piet
> Hein
> > > (via Tom White)
> > >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message