Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CAGQtxvZ9Qv7G+C1qMwP-tg82bpStbWin7_6SRY4OxBiR=SVpuQ@mail.gmail.com>
References: 
 <CANpG1OgLjCckwMLGOj=HHyYXy3McQh30Xn1UPy=oFCQM49n+FQ@mail.gmail.com>
 <CAGQtxvZ9Qv7G+C1qMwP-tg82bpStbWin7_6SRY4OxBiR=SVpuQ@mail.gmail.com>
From: David Nalley <david@gnsa.us>
Date: Fri, 22 May 2015 19:52:31 -0400
Message-ID: 
 <CAKprHVYN=VhT-dkEtBo8-e=Z-sG2OV1L5NEU7YVTLGQ0Pxwihg@mail.gmail.com>
Subject: Re: Jenkins build failures
To: "dev@cloudstack.apache.org" <dev@cloudstack.apache.org>
Content-Type: text/plain; charset=UTF-8

You are almost certainly not going to get access to the slaves.
I'll see if the Infra Jenkins guy can peer into what's going on and
why - though I think Rafael's later response is perhaps pragmatic.

--David

On Fri, May 22, 2015 at 1:43 PM, Daan Hoogland <daan.hoogland@gmail.com> wrote:
> I've been asking infra about this. i have no idea how to access those
> slaves. see https://issues.apache.org/jira/browse/BUILDS-81
>
> Op vr 22 mei 2015 om 19:37 schreef Rafael Fonseca <rsafonseca@gmail.com>:
>
>> Hi guys,
>>
>> This Jenkins build failure in OVM3 is starting to annoy me.. can anyone
>> help/grant access to the apache build site/slaves, either to add some
>> config to the Jenkins job to produce useful output on failures or to track
>> the issue on the failing slaves themselves?
>>
>> This is failing only on specific build hosts...
>>
>> Rafael
>>