I started a Wiki page on this at: http://wiki.apache.org/general/PreCommitBuilds
On May 17, 2011, at 1:15 AM, Nigel Daley wrote:
> It was just temporarily disabled while we worked out some changes. It's back
> on now.
>
> Cheers,
> Nige
>
> On May 16, 2011, at 2:55 PM, Grant Ingersoll wrote:
It was just temporarily disabled while we worked out some changes. It's back
on now.
Cheers,
Nige
On May 16, 2011, at 2:55 PM, Grant Ingersoll wrote:
> Nigel,
>
> I'm finally coming back to this and starting to investigate. I see the main
> Job is disabled at the moment. Is there something
Nigel,
I'm finally coming back to this and starting to investigate. I see the main
Job is disabled at the moment. Is there something else that is used?
-Grant
On Apr 10, 2011, at 11:20 AM, Nigel Daley wrote:
> Hey Grant. Sorry for the late reply.
>
> I revamped the precommit testing in the
Hey Grant. Sorry for the late reply.
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
> -Original Message-
> From: Grant Ingersoll [mailto:gsing...@apache.org]
> Sent: Thursday, 31 March 2011 1:38 AM
> To: builds@apache.org
> Subject: Hadoop patch builds for other Projects
>
> Over in Lucene, we interested in setting up a patch testing framework fo
Over in Lucene, we interested in setting up a patch testing framework for
Lucene similar to what Hadoop does. That is, when a new patch comes in, we
would like to apply it to the trunk, test it and check it if it meets our
requirements and then post a comment on the JIRA issue giving it a preli
Over in Lucene, we interested in setting up a patch testing framework for
Lucene similar to what Hadoop does. That is, when a new patch comes in, we
would like to apply it to the trunk, test it and check it if it meets our
requirements and then post a comment on the JIRA issue giving it a preli
