That's the idea (we can define what it does, i.e. run tests, check formatting, etc.) I'm still not entirely certain on the process, but am looking into it.
On May 16, 2011, at 7:04 PM, Lance Norskog wrote: > So, this takes patches one at a time and checks if they still apply > and work? Cool! > > On Mon, May 16, 2011 at 2:44 PM, Grant Ingersoll (JIRA) <[email protected]> > wrote: >> 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 >> >> >> 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 [email protected] >> {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. >> For more information on JIRA, see: http://www.atlassian.com/software/jira >> > > > > -- > Lance Norskog > [email protected]
