Fathi Boudra writes:
> On 18 May 2013 04:06, Kevin Hilman wrote:
>> Fathi Boudra writes:
>>
>> [...]
>>
Is there a way for us (linaro folks) to see more of the Jenkins setup
for these jobs (including the scripts.) There appears to be some useful
add-ons being used. Read-only acc
On 18 May 2013 10:12, Fathi Boudra wrote:
> On 18 May 2013 04:06, Kevin Hilman wrote:
>> Fathi Boudra writes:
>>
>> [...]
>>
>> Now that I have permission on linaro jenkins, I started experimenting
>> with trying to get something useful for ARM maintainers, and I created a
>> basic job[1] for bu
On 18 May 2013 04:06, Kevin Hilman wrote:
> Fathi Boudra writes:
>
> [...]
>
>>> Is there a way for us (linaro folks) to see more of the Jenkins setup
>>> for these jobs (including the scripts.) There appears to be some useful
>>> add-ons being used. Read-only access to the detailed configuratio
Fathi Boudra writes:
[...]
>> Is there a way for us (linaro folks) to see more of the Jenkins setup
>> for these jobs (including the scripts.) There appears to be some useful
>> add-ons being used. Read-only access to the detailed configuration of
>> the jenkins jobs would be very useful.
>
> Y
Fathi Boudra writes:
> On 14 May 2013 23:49, Kevin Hilman wrote:
>> Fathi Boudra writes:
>>
>> [...]
>>
Is there a way for us (linaro folks) to see more of the Jenkins setup
for these jobs (including the scripts.) There appears to be some useful
add-ons being used. Read-only acc
On 13 May 2013 11:12, Nicolas Dechesne
> also in the link above all of the 7
> 'active' jobs are failing with 3 of them who always failed, and 2 of them
> failing for 2 weeks. so it's not clear what that means.
I we have a look at one og the jobs that is "always failing" :
https://ci.linaro.org/
On 14 May 2013 23:49, Kevin Hilman wrote:
> Fathi Boudra writes:
>
> [...]
>
>>> Is there a way for us (linaro folks) to see more of the Jenkins setup
>>> for these jobs (including the scripts.) There appears to be some useful
>>> add-ons being used. Read-only access to the detailed configuratio
t;> > http://article.gmane.org/gmane.linux.ports.tegra/10683
> >> >
> >> > Seems there is lots desire for an improvement to automated build
> >> > coverage and automated reporting along with it.
> >>
> >> I replied to it. We've got already su
Fathi Boudra writes:
[...]
>> Is there a way for us (linaro folks) to see more of the Jenkins setup
>> for these jobs (including the scripts.) There appears to be some useful
>> add-ons being used. Read-only access to the detailed configuration of
>> the jenkins jobs would be very useful.
>
> Y
On 14 May 2013 21:52, Kevin Hilman wrote:
> I'll second Nicolas' comments.
>
> As a kernel developer and upstream maintainer (and now working for
> Linaro), it's not at all clear (or documented that I can find) how
> kernel CI is being structure and implemented nor how it could be useful
> for ker
; Seems there is lots desire for an improvement to automated build
>> > coverage and automated reporting along with it.
>>
>> I replied to it. We've got already such daily builds with boot
>> testing: https://ci.linaro.org/jenkins/view/kernel-ci
>>
>> I&#
/article.gmane.org/gmane.linux.ports.tegra/10683
>
> Seems there is lots desire for an improvement to automated build
> coverage and automated reporting along with it.
I replied to it. We've got already such daily builds with boot
testing: https://ci.linaro.org/jenkins/view/k
On Thu, May 9, 2013 at 7:56 PM, Fathi Boudra wrote:
> > Hi all,
> >
> > I just wanted to forward this thread from LAKML to linaro-dev:
> > http://article.gmane.org/gmane.linux.ports.tegra/10683
> >
> > Seems there is lots desire for an improvement to automa
On 9 May 2013 20:03, Mike Turquette wrote:
> Hi all,
>
> I just wanted to forward this thread from LAKML to linaro-dev:
> http://article.gmane.org/gmane.linux.ports.tegra/10683
>
> Seems there is lots desire for an improvement to automated build
> coverage and automated re
Hi all,
I just wanted to forward this thread from LAKML to linaro-dev:
http://article.gmane.org/gmane.linux.ports.tegra/10683
Seems there is lots desire for an improvement to automated build
coverage and automated reporting along with it.
Regards,
Mike
15 matches
Mail list logo
