On Tue, Jul 2, 2019 at 11:56 PM Jarek Potiuk <pot...@apache.org> wrote: >...
> In the meantime maybe INFRA can help to coordinate some effort between > Flink/Arrow/Airflow to decrease pressure on Travis? We considered few > options (and are going to implement some of them shortly I think). Some of > them are not direct changes in Travis CI builds but some other > workflow/infrastructure changes that will decrease pressure on Travis: > >... > Maybe the committers from Flink and Arrow can also take a look at > non-obvious ways how their projects can decrease pressure on Travis (at > least for the time being). Maybe there are some quick wins we can apply in > short time in coordinated way and buy more time for switching the > infrastructure ? > The above is fabulous. Please continue trading thoughts and working to reduce your Travis loads, for your own benefit and for your fellow projects at the Foundation. This list is the best space to trade such ideas. I'm not sure what Infra can do, as our skillset is quite a bit different from what your projects need, for reducing load. We'll keep this list apprised of anything we find. If anybody knows of, and/or can recommend a similar type of outsourced build service ... we *absolutely* would welcome pointers. We're gonna keep Jenkins and buildbot around for the foreseeable future, and are interested in outsourced solutions. Cheers, Greg Stein Infrastructure Administrator, ASF
