lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Grant Ingersoll (JIRA)" <>
Subject [jira] [Commented] (LUCENE-3104) Hook up Automated Patch Checking for Lucene/Solr
Date Thu, 19 May 2011 20:42:47 GMT


Grant Ingersoll commented on LUCENE-3104:

Here's an example of running just the
./ DEV ../../../patches/LUCENE-3120.patch /path/trunk-clean/build/patches /usr/bin/svn
/usr/bin/grep /usr/bin/patch /path/lucene/dev/trunk-clean

Note, the directory where you are applying the patch (trunk-clean) must be clear of all mods.

> Hook up Automated Patch Checking for Lucene/Solr
> ------------------------------------------------
>                 Key: LUCENE-3104
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Task
>            Reporter: Grant Ingersoll
>         Attachments: LUCENE-3104.patch
> 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
> {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.
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message