I've been poking around on the Arrow website and wiki and I can't find documentation relating to CI. Do we have any documentation on how things work today or what the goals are? For Rust builds it isn't immediately obvious why they are building on both Travis CI and Ursabot.
On Fri, Sep 27, 2019 at 6:33 AM Wes McKinney <wesmck...@gmail.com> wrote: > FYI, using the kibble.dev link from INFRA-18533, it seems that this > September we're using about 15% of the ASF's total Travis CI capacity > (60 concurrent workers I think) > > https://imgur.com/a/oOrbPsj > > The highest is Apache Druid (incubating) at 18%, so we are #2. Suffice > to say the ASF's Travis couldn't accommodate us if we had twice as > many pull requests > > On Fri, Sep 27, 2019 at 7:26 AM Wes McKinney <wesmck...@gmail.com> wrote: > > > > I've been sounding the alarm bells about this for a while. We need to > > work to get ourselves off of Travis CI, but it is not going to be > > easy. > > > > On Thu, Sep 26, 2019 at 11:42 PM Micah Kornfield <emkornfi...@gmail.com> > wrote: > > > > > > My understanding is the Travis CI queue is shared among all apache > > > projects, and there are few including Arrow that make heavy use of the > > > resources. Hence, a lot of time waiting for jobs to start. I think > there > > > are some open JIRAs to finish dockerization of builds, I don't know the > > > current status of finding alternative CI sources though. > > > > > > On Thu, Sep 26, 2019 at 10:24 PM Andy Grove <andygrov...@gmail.com> > wrote: > > > > > > > I know this has been discussed in the past, and I apologize for not > paying > > > > attention at the time (and searching for arrow + travis in email > isn't very > > > > effective) but why does it take so long for our Travis CI builds and > are > > > > there open JIRA issues related to this? > > > > > > > > Thanks, > > > > > > > > Andy. > > > > >
