Re: CI for Brooklyn

[Richard Downer <ri...@apache.org>]

Andrew,

Kicking this thread back into life. I notice that I don't have the
option to modify our Jenkins build job - I assume this is because I
don't have the necessary Jenkins privileges. Are you able to give this
privilege to all of the Brooklyn committers?

If I can get privileges, I can look into sending Jenkins build
failures to the list, as we discussed earlier in this thread.

Thanks
Richard.


On 1 July 2014 10:20, Aled Sage <al...@gmail.com> wrote:
> +1 to e-mailing failures to dev@brooklyn.
>
> +1 to Richard's observation - we should not run integration tests on shared
> infrastructure; let's continue to use the jenkins box that cloudsoft
> contribute.
>
> Andrew, have you looked at setting up buildhive to run against all pull
> requests on https://github.com/apache/incubator-brooklyn?
> I really miss that! PRs are sometimes getting merged without anyone checking
> if the tests still pass!
>
> Aled
>
>
>
> On 01/07/2014 09:59, Richard Downer wrote:
>>
>> On 30 June 2014 21:01, Andrew Kennedy <an...@cloudsoftcorp.com>
>> wrote:
>>>
>>> Any objections (or other ideas) about sending results of failing builds
>>> on
>>> Jenkins to the list?
>>
>> +1
>> It simply needs to be done... it's a pain because it generates noise,
>> but the alternative - that nobody ever looks at Jenkins - is worse.
>>
>> One other comment, I see you added a note to the Jenkins job saying
>> you were intending to run the integration tests as part of the job.
>> Since the integration tests can be starting processes, opening ports,
>> etc. (and a buggy entity or test could leave these behind), is it wise
>> to run this on shared infrastructure?
>>
>> Richard.
>
>

Re: CI for Brooklyn

[Richard Downer <ri...@apache.org>]

Svet,

I've switched off the "abort the build if it's stuck" option - once
we've got a run of successful builds and know the typical time, I can
switch it back on again.

Richard.

On 27 September 2014 10:44, Svetoslav Neykov
<sv...@cloudsoftcorp.com> wrote:
> Richard,
>
> Could you look into extending the timeout period for the build. A lot of builds failed around the 20th minute due to this restriction.
>
> Svet.
>
> -----Original Message-----
> From: David Nalley [mailto:david@gnsa.us]
> Sent: Friday, September 26, 2014 11:23 PM
> To: dev@brooklyn.incubator.apache.org
> Subject: Re: CI for Brooklyn
>
> On Thu, Sep 25, 2014 at 11:36 AM, Richard Downer <ri...@apache.org> wrote:
>> Andrew,
>>
>> Kicking this thread back into life. I notice that I don't have the
>> option to modify our Jenkins build job - I assume this is because I
>> don't have the necessary Jenkins privileges. Are you able to give this
>> privilege to all of the Brooklyn committers?
>>
>
> Any officer can give them the requisite karma. Though, concept of least-privilege suggests we should only grant to those who actually wish to exercise those privileges.
>
>> If I can get privileges, I can look into sending Jenkins build
>> failures to the list, as we discussed earlier in this thread.
>>
>
> Done - you now have karma for that. (login to builds.a.o with your LDAP creds)
>
> --David
>

RE: CI for Brooklyn

[Svetoslav Neykov <sv...@cloudsoftcorp.com>]

Richard,

Could you look into extending the timeout period for the build. A lot of builds failed around the 20th minute due to this restriction.

Svet.

-----Original Message-----
From: David Nalley [mailto:david@gnsa.us] 
Sent: Friday, September 26, 2014 11:23 PM
To: dev@brooklyn.incubator.apache.org
Subject: Re: CI for Brooklyn

On Thu, Sep 25, 2014 at 11:36 AM, Richard Downer <ri...@apache.org> wrote:
> Andrew,
>
> Kicking this thread back into life. I notice that I don't have the 
> option to modify our Jenkins build job - I assume this is because I 
> don't have the necessary Jenkins privileges. Are you able to give this 
> privilege to all of the Brooklyn committers?
>

Any officer can give them the requisite karma. Though, concept of least-privilege suggests we should only grant to those who actually wish to exercise those privileges.

> If I can get privileges, I can look into sending Jenkins build 
> failures to the list, as we discussed earlier in this thread.
>

Done - you now have karma for that. (login to builds.a.o with your LDAP creds)

--David

Re: CI for Brooklyn

[David Nalley <da...@gnsa.us>]

On Thu, Sep 25, 2014 at 11:36 AM, Richard Downer <ri...@apache.org> wrote:
> Andrew,
>
> Kicking this thread back into life. I notice that I don't have the
> option to modify our Jenkins build job - I assume this is because I
> don't have the necessary Jenkins privileges. Are you able to give this
> privilege to all of the Brooklyn committers?
>

Any officer can give them the requisite karma. Though, concept of
least-privilege suggests we should only grant to those who actually
wish to exercise those privileges.

> If I can get privileges, I can look into sending Jenkins build
> failures to the list, as we discussed earlier in this thread.
>

Done - you now have karma for that. (login to builds.a.o with your LDAP creds)

--David