Hello all,
Krisztián has been lately working on getting Buildbot running for Arrow. While
I have not yet had the time to look at it in detail what would hinder us using
it as the main Linux builder and ditching Travis except for OSX?
Otherwise I have lately made really good experiences with Gitlab CI connected
to Github projects. While they only offer a comparatively small amount of CI
time per month per project (2000 minutes is quite small in the Arrow case), I
enjoyed that you can connect your own builders to their hosted gitlab.com
instance. This would enable us to easily add funded workers to the project as
well as utilise special hardware that we would not otherwise get in public CI
instances. The CI runners ("workers") are really simple to setup (It took me on
Windows and on Linux less than 5min each) and the logs show up in the hosted UI.
Uwe
On Thu, May 30, 2019, at 8:28 PM, Wes McKinney wrote:
> hi folks,
>
> Over the last several months we have probably been overutilizing the
> ASF's Travis CI capacity; it seems that we are being limited as of
> very recently to 5 concurrent build workers so CI feedback is taking
> longer.
>
> We have an INFRA ticket about the issue here
>
> https://issues.apache.org/jira/browse/INFRA-18533
>
> If anyone has funding available to help pay for additional CI capacity
> for Apache Arrow please let me know online or offline. We will assess
> our options based on what the Infrastructure team says
>
> thanks,
> Wes
>
