[ 
https://issues.apache.org/jira/browse/ARROW-13059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jonathan Keane closed ARROW-13059.
----------------------------------
    Resolution: Duplicate

> [Dev] Adapt the crossbow code to save build status to json
> ----------------------------------------------------------
>
>                 Key: ARROW-13059
>                 URL: https://issues.apache.org/jira/browse/ARROW-13059
>             Project: Apache Arrow
>          Issue Type: Sub-task
>          Components: Developer Tools
>            Reporter: Jonathan Keane
>            Assignee: Mauricio 'PachĂĄ' Vargas SepĂșlveda
>            Priority: Major
>
> Add to / adapt the code that {{archery crossbow}} already uses to send the 
> email report to also save the status of the builds to a json file and commit 
> that to a new branch in the crossbow (or some other ursacomputing repository)
> Crossbow code (hint this is the code that you will want to copy + adapt to do 
> this new task): 
> https://github.com/apache/arrow/blob/master/dev/archery/archery/crossbow/reports.py
> This is how the nightly jobs are triggered: 
> https://github.com/ursacomputing/crossbow/blob/master/.github/workflows/nightly_report.yml
> (note that it [figures out what the job 
> id|https://github.com/ursacomputing/crossbow/blob/master/.github/workflows/nightly_report.yml#L33-L34]
>  is and then it runs a command {{archery crossbow report ...}}
> The archer CLI interface is specifiedin 
> https://github.com/apache/arrow/blob/master/dev/archery/archery/crossbow/cli.py
> Ultimately what we want is something like: a new command like {{crossbow 
> archery save-report-data}} that uses similar code/approaches to how the 
> report is designed but saves the data to json (or line delimited json) and 
> saves that somewhere reliable (i.e. the ursacomputing/crossbow repository or 
> a new repository under ursacomputing)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to