[
https://issues.apache.org/jira/browse/ARROW-2792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16538923#comment-16538923
]
Krisztian Szucs commented on ARROW-2792:
----------------------------------------
How about creating a release tag for each task (instead of the job)? That way
We would avoid name collisions.
Should We be explicit about the artifact names? We can render the deploy
segment with jinja2.
> [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)
