[ https://issues.apache.org/jira/browse/ARROW-12846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated ARROW-12846: ----------------------------------- Labels: pull-request-available (was: ) > [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: Critical > Labels: pull-request-available > Fix For: 6.0.0 > > Time Spent: 10m > Remaining Estimate: 0h > > 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)