You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@arrow.apache.org by "Jorge Leitão (Jira)" <ji...@apache.org> on 2021/05/21 04:47:00 UTC
[jira] [Commented] (ARROW-12846) [Release] Improve upload of
binaries
[ https://issues.apache.org/jira/browse/ARROW-12846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17348964#comment-17348964 ]
Jorge Leitão commented on ARROW-12846:
--------------------------------------
Got it. I am currently running it, so not sure how artifactory behaves. The command I am using:
```CROSSBOW_JOB_NUMBER=2 dev/release/05-binary-upload.sh 4.0.1 1```
> [Release] Improve upload of binaries
> ------------------------------------
>
> Key: ARROW-12846
> URL: https://issues.apache.org/jira/browse/ARROW-12846
> Project: Apache Arrow
> Issue Type: Improvement
> Components: Developer Tools
> Reporter: Jorge Leitão
> Assignee: Kouhei Sutou
> Priority: Major
>
> Running dev/release/05-binary-upload.sh takes a long time and is prone to network failures, etc. When it fails, it needs to be started from scratch.
> IMO we could alleviate this. An idea here would be to run the script in the same order of the configuration variables that it has (e.g. `UPLOAD_AMAZON_LINUX_RPM`) and echo the variable when binaries corresponding to that section are complete.
> This way, when something fails, as a user I can pass r.g. `UPLOAD_AMAZON_LINUX_RPM=0` and skip the parts that were already uploaded.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)