Hook up Automated Patch Checking for Lucene/Solr [LUCENE-3104]

It would be really great if we could get feedback to contributors sooner on many things that are basic (tests exist, patch applies cleanly, etc.)

From Nigel Daley on builds@a.o
> 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/

---
Migrated from [LUCENE-3104](https://issues.apache.org/jira/browse/LUCENE-3104) by Grant Ingersoll (@gsingers), updated May 19 2011
Attachments: [LUCENE-3104.patch](https://apache.github.io/lucene-jira-archive/attachments/LUCENE-3104/LUCENE-3104.patch)

Start with the PreCommit-Admin job documentation and configuration, then review the referenced PreCommit-HADOOP-Build, PreCommit-MAPREDUCE-Build, and PreCommit-HDFS-Build jobs. Determine the downstream job setup needed for Lucene/Solr and the Jira filter update; done means contributors receive automated feedback on patch application and existing tests.

Written by the indexing model from the issue text.