On Fri, Oct 30, 2015 at 7:05 AM, Rajani Karuturi <[email protected]> wrote: +1'ed
and further > On Fri, Oct 30, 2015 at 4:55 AM, David Nalley <[email protected]> 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 <[email protected]> > > 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
