You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mahout.apache.org by "Sean Owen (JIRA)" <ji...@apache.org> on 2012/06/22 18:10:44 UTC
[jira] [Resolved] (MAHOUT-698) Hook up Automated Patch Checking for
Mahout
[ https://issues.apache.org/jira/browse/MAHOUT-698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
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: https://issues.apache.org/jira/browse/MAHOUT-698
> 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
> https://builds.apache.org/hudson/job/PreCommit-Admin/
> 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 (https://issues.apache.org/jira/sr/jira.issueviews:searchrequest-xml/12313474/SearchRequest-12313474.xml?tempMax=100 ) 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:
> https://builds.apache.org/hudson/job/PreCommit-HADOOP-Build/
> https://builds.apache.org/hudson/job/PreCommit-MAPREDUCE-Build/
> https://builds.apache.org/hudson/job/PreCommit-HDFS-Build/
> {quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [jira] [Resolved] (MAHOUT-698) Hook up Automated Patch Checking
for Mahout
Posted by Sean Owen <sr...@gmail.com>.
Oops maybe I missed the date of last update. Take it back if you are
working on it.
On Jun 22, 2012 9:44 PM, "Robin Anil" <ro...@gmail.com> wrote:
> But I just started on it fresh last week? This is too harsh.
> On Jun 22, 2012 11:10 AM, "Sean Owen (JIRA)" <ji...@apache.org> wrote:
>
> >
> > [
> >
> https://issues.apache.org/jira/browse/MAHOUT-698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
> ]
> >
> > 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: https://issues.apache.org/jira/browse/MAHOUT-698
> > > 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
> > > https://builds.apache.org/hudson/job/PreCommit-Admin/
> > > 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 (
> >
> https://issues.apache.org/jira/sr/jira.issueviews:searchrequest-xml/12313474/SearchRequest-12313474.xml?tempMax=100)
> 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:
> > > https://builds.apache.org/hudson/job/PreCommit-HADOOP-Build/
> > > https://builds.apache.org/hudson/job/PreCommit-MAPREDUCE-Build/
> > > https://builds.apache.org/hudson/job/PreCommit-HDFS-Build/
> > > {quote}
> >
> > --
> > This message is automatically generated by JIRA.
> > If you think it was sent incorrectly, please contact your JIRA
> > administrators:
> > https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
> > For more information on JIRA, see:
> http://www.atlassian.com/software/jira
> >
> >
> >
>
Re: [jira] [Resolved] (MAHOUT-698) Hook up Automated Patch Checking
for Mahout
Posted by Robin Anil <ro...@gmail.com>.
But I just started on it fresh last week? This is too harsh.
On Jun 22, 2012 11:10 AM, "Sean Owen (JIRA)" <ji...@apache.org> wrote:
>
> [
> https://issues.apache.org/jira/browse/MAHOUT-698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel]
>
> 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: https://issues.apache.org/jira/browse/MAHOUT-698
> > 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
> > https://builds.apache.org/hudson/job/PreCommit-Admin/
> > 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 (
> https://issues.apache.org/jira/sr/jira.issueviews:searchrequest-xml/12313474/SearchRequest-12313474.xml?tempMax=100) 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:
> > https://builds.apache.org/hudson/job/PreCommit-HADOOP-Build/
> > https://builds.apache.org/hudson/job/PreCommit-MAPREDUCE-Build/
> > https://builds.apache.org/hudson/job/PreCommit-HDFS-Build/
> > {quote}
>
> --
> This message is automatically generated by JIRA.
> If you think it was sent incorrectly, please contact your JIRA
> administrators:
> https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
> For more information on JIRA, see: http://www.atlassian.com/software/jira
>
>
>