mahout-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Owen (JIRA)" <>
Subject [jira] [Resolved] (MAHOUT-698) Hook up Automated Patch Checking for Mahout
Date Fri, 22 Jun 2012 16:10:44 GMT


Sean Owen resolved MAHOUT-698.

    Resolution: Won't Fix

Don't think Robin ever did this. If nobody's going to do it in a year and it's not critical
and would introduce more overhead, I think we kill it.
> Hook up Automated Patch Checking for Mahout
> -------------------------------------------
>                 Key: MAHOUT-698
>                 URL:
>             Project: Mahout
>          Issue Type: Task
>            Reporter: Grant Ingersoll
>            Assignee: Robin Anil
> It would be great if we could get feedback to contributors on the basics of patches (tests
exist/pass, applies cleanly, formatting, etc.)
> From Nigel Daley on builds@a.o
> {quote}
> I revamped the precommit testing in the fall so that it doesn't use Jira email anymore
to trigger a build.  The process is controlled by
> which has some documentation up at the top of the job.  You can look at the config of
the job (do you have access?) to see what it's doing.  Any project could use this same admin
job -- you just need to ask me to add the project to the Jira filter used by the admin job
) once you have the downstream job(s) setup for your specific project.  For Hadoop we have
3 downstream builds configured which also have some documentation:
> {quote}

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message