FYI builds@ resolved the issue, I've reverted back to our previous
configuration and everything seems ok at this point.

On Thu, Aug 25, 2011 at 11:05 PM, Mahadev Konar <maha...@hortonworks.com> wrote:
> Thanks Pat!
>
> mahadev
>
> On Wed, Aug 24, 2011 at 3:19 PM, Patrick Hunt <ph...@apache.org> wrote:
>> builds@ jenkins seems to be borked - I had to turn off a number of
>> plugins before it started passing again. I've notified builds@ but
>> they are currently unable to clear the issue.
>>
>> For the time being jenkins will not report findbugs/warnings/clover
>> results - however these tests are still running. We should be ok for
>> now.
>>
>> Patrick
>>
>> On Wed, Aug 24, 2011 at 9:52 AM, Patrick Hunt <ph...@apache.org> wrote:
>>> recent trunk builds have been failing due to some issue with the
>>> findbugs jenkins plugin on build@. I've notified builds@ and turned
>>> off the jenkins plugin for the time being, this should clear up the
>>> issue.
>>>
>>> Patrick
>>>
>>
>

Reply via email to