The QA bot was previously pointing at a JIRA filter which matched all
Patch Available issues. That number has grown to >300 across the many
projects that the QA bot works on. Unfortunately, that meant that a
lot of the newer JIRAs (especially in alphabetically lower projects
like HBASE, HADOOP, and GIRAPH) weren't getting picked up. I duped the
filter, restricted it to those PA issues updated in the last 2 weeks,
and changed the jenkins PreCommit-Admin job to point to the new one.
It seems to have now unstuck itself and is processing a bunch of
attachments that it had fallen behind on.

Thanks
-Todd
--
Todd Lipcon
Software Engineer, Cloudera

Thanks Todd!

On Wed, Dec 12, 2012 at 6:34 PM, Todd Lipcon <[EMAIL PROTECTED]> wrote:

> The QA bot was previously pointing at a JIRA filter which matched all
> Patch Available issues. That number has grown to >300 across the many
> projects that the QA bot works on. Unfortunately, that meant that a
> lot of the newer JIRAs (especially in alphabetically lower projects
> like HBASE, HADOOP, and GIRAPH) weren't getting picked up. I duped the
> filter, restricted it to those PA issues updated in the last 2 weeks,
> and changed the jenkins PreCommit-Admin job to point to the new one.
> It seems to have now unstuck itself and is processing a bunch of
> attachments that it had fallen behind on.
>
> Thanks
> -Todd
> --
> Todd Lipcon
> Software Engineer, Cloudera
>

Thanks Todd.
On Thu, Dec 13, 2012 at 9:44 AM, Nick Dimiduk <[EMAIL PROTECTED]> wrote:

> Thanks Todd!
>
> On Wed, Dec 12, 2012 at 6:34 PM, Todd Lipcon <[EMAIL PROTECTED]> wrote:
>
> > The QA bot was previously pointing at a JIRA filter which matched all
> > Patch Available issues. That number has grown to >300 across the many
> > projects that the QA bot works on. Unfortunately, that meant that a
> > lot of the newer JIRAs (especially in alphabetically lower projects
> > like HBASE, HADOOP, and GIRAPH) weren't getting picked up. I duped the
> > filter, restricted it to those PA issues updated in the last 2 weeks,
> > and changed the jenkins PreCommit-Admin job to point to the new one.
> > It seems to have now unstuck itself and is processing a bunch of
> > attachments that it had fallen behind on.
> >
> > Thanks
> > -Todd
> > --
> > Todd Lipcon
> > Software Engineer, Cloudera
> >
>