[
https://issues.apache.org/jira/browse/ARROW-2792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16539005#comment-16539005
]
Krisztian Szucs commented on ARROW-2792:
----------------------------------------
[~wesmckinn] We probably need to split the builds (define matrix in tasks.yml
instead of the templates), because linux packages starts to timeout on travis
and to prevent artifact collisions within a single task.
Something like:
{code}
wheel-win:
platform: win
template: python-wheels/appveyor.yml
matrix:
cp35: # variant
generator: Visual Studio 14 2015 Win64
numpy: "1.13"
python: "3.5"
cp36:
generator: Visual Studio 14 2015 Win64
numpy: "1.13"
python: "3.6"
artifacts:
- pyarrow-{version}-{variant}-{variant}m-win_amd64.whl
- pyarrow-{version}-{variant}-{variant}m-win_amd64.whl
{code}
I'm not exactly sure on the matrix definition though.
> [Packaging] Consider uploading tarballs to avoid naming conflicts
> -----------------------------------------------------------------
>
> Key: ARROW-2792
> URL: https://issues.apache.org/jira/browse/ARROW-2792
> Project: Apache Arrow
> Issue Type: Task
> Components: Packaging
> Reporter: Krisztian Szucs
> Priority: Major
> Fix For: 0.10.0
>
>
> [~kou] has suggested, that we should upload tarballs for linux package
> builds, to include all .deb and/or .rpm packages.
> For conda packages currenlty we postfix the artifacts with the arch name to
> avoid naming conflicts. To remain consistent we should chose one of the
> strategies (postifx or tarballs) and apply for each tasks.
> However tarballs would be a trivial solution to resolve naming conflicts,
> ensuring that a tarball contains all of the expected artifacts would require
> to download and extract it beforehand. This requires changes in status checks
> and artifact downloading / signing.
> [~cpcloud] thoughts?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
