Subject: Re: [boost] Purchasing Travis Resources for boostorg (was Re: [1.65.0] Point release?)
From: Alexander Zaitsev (zamazan4ik_at_[hidden])
Date: 2017-08-27 16:58:57
27.08.2017 15:21, Tom Kent via Boost Ð¿Ð¸ÑÐµÑ:
> 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]>
>>> Daniel James wrote:
>>> But we don't rely that much on the testers nowadays, so this would be
>>> 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?
> Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Here you can see some results about using Travis CI additionally to
Boost's test system: https://travis-ci.org/ZaMaZaN4iK/boost_indirect_testing
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk