[
https://issues.apache.org/jira/browse/ARROW-5914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16883681#comment-16883681
]
Uwe L. Korn commented on ARROW-5914:
------------------------------------
[~fsaintjacques][~kszucs][~wesmckinn] This is why we have used conda in these
builds. I have the great fear that we rely more and on more on manual building
of thirdparty dependencies in our build scripts which just adds more
maintenance overhead. I was so frustrated with the manual scripts in the
manylinux1 one case that I was considering in making a manylinux1 conda channel
to build the dependencies. This would have greatly reduced my pain in the
maintenance of the manylinux1 container.
We need to test against system dependencies but then we should do this as we
were doing this previously in the nightlies.
> [CI] Build bundled dependencies in docker build step
> ----------------------------------------------------
>
> Key: ARROW-5914
> URL: https://issues.apache.org/jira/browse/ARROW-5914
> Project: Apache Arrow
> Issue Type: Improvement
> Components: Continuous Integration
> Reporter: Francois Saint-Jacques
> Priority: Minor
> Fix For: 1.0.0
>
>
> In the recently introduced ARROW-5803, some heavy dependencies (thrift,
> protobuf, flatbufers, grpc) are build at each invocation of docker-compose
> build (thus each travis test).
> We should aim to build the third party dependencies in docker build phase
> instead, to exploit caching and docker-compose pull so that the CI step
> doesn't need to build said dependencies each time.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
