cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daan Hoogland <daan.hoogl...@gmail.com>
Subject Re: [PROPOSAL] remove travis pull request checks from github
Date Fri, 30 Oct 2015 11:11:18 GMT
On Fri, Oct 30, 2015 at 7:05 AM, Rajani Karuturi <rajani@apache.org> wrote:
​+1'ed

and further

> On Fri, Oct 30, 2015 at 4:55 AM, David Nalley <david@gnsa.us> wrote:
>
> > 2 hours before this message was sent, there was a message about
> > jenkins being unreliable.
>
​both are not perfect, travis is costing RMs and their minions, and
contributors time!​



> >
> > So I am starting to think that something other than Travis or Jenkins
> > is the problem.
>
​No, Jenkins and Travis are problems! maintenance wise they are costing
effort we are not putting into it.​


>
> > --David
> >
> > On Thu, Oct 29, 2015 at 5:33 PM, Daan Hoogland <daan.hoogland@gmail.com>
> > wrote:
> > > Guys and dolls,
> > >
> > > We have been having travis builds for a while now and they seem to
> > generate
> > > more work then help. There are a lot of time-outs, (false positive) and
> > > when a suite passes it is often because all tests where skipped (false
> > > negative). In addition, and this may be just me, I've never been able
> to
> > > pinpoint a problem based on travis output.
> > >
> > > therefore:
> > >
> > > I move that we completely disable travis runs on PRs to the cloudstack
> > > project. This will reduce confusion about whether a PR is good and will
> > > reduce the need for willing contributers to force push their branch
> over
> > > and over.
> > >
> > > --
> > > Daan
> >
>



-- 
Daan

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message