reef-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mariia Mykhailova <mamyk...@microsoft.com>
Subject RE: What about turning off Jenkins?
Date Tue, 31 May 2016 18:38:30 GMT
-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.
Mime
View raw message