[ 
https://issues.apache.org/jira/browse/ARROW-2676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16508653#comment-16508653
 ] 

Wes McKinney commented on ARROW-2676:
-------------------------------------

Wanted to repeat my comments from GitHub 
(https://github.com/apache/arrow/pull/1869#issuecomment-393693957) here to 
explain the desired workflow:

For each run of the job creation tool (i.e. the current crossbow.py)

* Create a separate tagged branch that contains a YAML file indicating the 
information about each task created as part of the run. So there should be one 
entry for each job that was created -- the git hash for the task, the CI 
service used to run the task, etc. It should also indicate if one or more 
artifacts are expected to be uploaded

* Tasks should be configured with the tag name, and artifacts should be 
uploaded to GitHub under the tag which should appear as a release on the repo

* We write a status tool which can query the status of a particular run and 
determine if the run is complete

* We write a tool to download all artifacts associated with a particular run 
and sign them with the release manager's GPG key

So here's what I'm expecting:

{code}
$ python crossbow.py ...
...
Job run tag: build-1234

$ python check-build-status.py build-1234
Task 1 on Travis CI completed
...
Task N on AppVeyor still running

$ python check-build-status.py build-1234
...
All tasks completed

$ python download-build-artifacts.py build-1234 --sign
{code} 

Here are the boxes we need to check:

* Can we run each desired task in a particular CI service? (the MVP for this is 
ARROW-2430)
* We can determine the list of created tasks associated with a particular run
* Each task can upload its artifacts to a deterministic central location (e.g. 
GitHub), where the artifacts are not commingled with any other run (that's this 
issue ARROW-2676)
* We can determine whether all the expected artifacts from a particular run 
have been successfully uploaded (i.e. to GitHub)
* We can, in an automated way and without clicking on a webpage, download all 
the artifacts from a successful run and GPG sign them for purposes of a release 
vote

> [Packaging] Deploy build artifacts to github releases
> -----------------------------------------------------
>
>                 Key: ARROW-2676
>                 URL: https://issues.apache.org/jira/browse/ARROW-2676
>             Project: Apache Arrow
>          Issue Type: Improvement
>          Components: Packaging
>            Reporter: Krisztian Szucs
>            Assignee: Krisztian Szucs
>            Priority: Major
>             Fix For: 0.10.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to