Subject: Re: [boost] Purchasing Travis Resources for boostorg (was Re: [1.65.0] Point release?)
From: Rene Rivera (grafikrobot_at_[hidden])
Date: 2017-08-27 12:52:22
On Sun, Aug 27, 2017 at 7:21 AM, Tom Kent via Boost <boost_at_[hidden]>
> On Sat, Aug 26, 2017 at 1:16 PM, Daniel James via Boost <
> boost_at_[hidden]> wrote:
> > On 26 August 2017 at 18:02, Peter Dimov via Boost <boost_at_[hidden]
> > wrote:
> > > Daniel James wrote:
> > > But we don't rely that much on the testers nowadays, so this would be
> > less
> > > of an issue.
> > I do. The turnaround on Travis is pretty terrible at the moment, and
> > that's going to get worse as more modules use it.
> While I'm a big fan of Boost's test system, and believe that it is an
> awesome resource that can't be replicated on the common CI services (lots
> of platforms and compiler versions/configs!), I also think that good
> per-commit CI on a service like travis is hugely important. Maybe someone
> should present a proposal to the steering committee to start paying for
> boostorg's account to have additional build resources?
FYI.. OSS Travis gives out 5 concurrent jobs. Which you can compare with
their paid plans: <https://travis-ci.com/plans>.
-- Rene Rivera
-- Grafik - Don't Assume Anything
-- Robot Dreams - http://robot-dreams.net
-- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail