What about turning off Jenkins?

[Dongjoon Hyun <do...@apache.org>]

Hi, All.

What about turning off Jenkins for now?

If possible, we can give Jenkins another proper roles for our project.

Warmly,
Dongjoon.

RE: What about turning off Jenkins?

[Mariia Mykhailova <ma...@microsoft.com>]

We can create separate Jenkins jobs for any role we want regardless of whether we disable or enable our current Java testing job. We used to have several Jenkins jobs previously, and it's possible to create more without affecting this one.

-Mariia

> Making new SNAPSHOT builds available in a repository comes to mind, either nightly or in reaction to commits to `master`.

> For now, just Github-bot (detecting new PRs and adds links to the related JIRA).

Re: What about turning off Jenkins?

[Markus Weimer <ma...@weimo.de>]

On 2016-05-31 11:38 AM, Mariia Mykhailova wrote:
> What kind of another proper roles do you have in mind?

Making new SNAPSHOT builds available in a repository comes to mind, 
either nightly or in reaction to commits to `master`.

Markus

Re: What about turning off Jenkins?

[Dongjoon Hyun <do...@apache.org>]

Oh, I see. You are working on that. :)

For now, just Github-bot (detecting new PRs and adds links to the related
JIRA).

Anyway, thank you for your efforts on our build systems!

Dongjoon.

On Tue, May 31, 2016 at 11:38 AM, Mariia Mykhailova <ma...@microsoft.com>
wrote:

> -1
> Jenkins environment is significantly different from Travis, and while it
> can by fairly noisy at times, at other times it displays test failures
> which Travis doesn't, and which ideally we should note and investigate.
> For now I've updated pre-build script to remove commands which have been
> failing for the past weeks (I've put them there previously to remedy
> another series of failures related to file corruption, so they are safe to
> remove). This should improve the state of things
>
> What kind of another proper roles do you have in mind? When I was looking
> at extending Jenkins use to test our .NET code (which theoretically it is
> capable of), I've found it hard because this instance of Jenkins and
> underlying build servers are managed by infra team, so we're not free to
> install whatever we want there (a newer version of .NET in our case).
>
> -Mariia
>
> -----Original Message-----
> From: Dongjoon Hyun [mailto:dongjoon@apache.org]
> Sent: Sunday, May 29, 2016 12:37 AM
> To: dev@reef.apache.org
> Subject: What about turning off Jenkins?
>
> Hi, All.
>
> What about turning off Jenkins for now?
>
> If possible, we can give Jenkins another proper roles for our project.
>
> Warmly,
> Dongjoon.
>

RE: What about turning off Jenkins?

[Mariia Mykhailova <ma...@microsoft.com>]

-1
Jenkins environment is significantly different from Travis, and while it can by fairly noisy at times, at other times it displays test failures which Travis doesn't, and which ideally we should note and investigate.
For now I've updated pre-build script to remove commands which have been failing for the past weeks (I've put them there previously to remedy another series of failures related to file corruption, so they are safe to remove). This should improve the state of things

What kind of another proper roles do you have in mind? When I was looking at extending Jenkins use to test our .NET code (which theoretically it is capable of), I've found it hard because this instance of Jenkins and underlying build servers are managed by infra team, so we're not free to install whatever we want there (a newer version of .NET in our case).

-Mariia

-----Original Message-----
From: Dongjoon Hyun [mailto:dongjoon@apache.org] 
Sent: Sunday, May 29, 2016 12:37 AM
To: dev@reef.apache.org
Subject: What about turning off Jenkins?

Hi, All.

What about turning off Jenkins for now?

If possible, we can give Jenkins another proper roles for our project.

Warmly,
Dongjoon.