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

Uwe L. Korn updated ARROW-4649:
-------------------------------
    Description: 
Now that we have an Arrow homebrew formula again and we may want to have it as 
a simple setup for R Arrow users, we should add a nightly crossbow task that 
checks whether this still builds fine.

To implement this, one should write a new travis.yml like 
[https://github.com/apache/arrow/blob/master/dev/tasks/python-wheels/travis.osx.yml]
 that calls {{brew install apache-arrow --HEAD}}. This task should then be 
added to https://github.com/apache/arrow/blob/master/dev/tasks/tests.yml so 
that it is executed as part of the nightly chain.

  was:Now that we have an Arrow homebrew formula again and we may want to have 
it as a simple setup for R Arrow users, we should add a nightly crossbow task 
that checks whether this still builds fine.


> [C++/CI/R] Add nightly job that builds `brew install apache-arrow --HEAD`
> -------------------------------------------------------------------------
>
>                 Key: ARROW-4649
>                 URL: https://issues.apache.org/jira/browse/ARROW-4649
>             Project: Apache Arrow
>          Issue Type: Bug
>          Components: C++, Continuous Integration, R
>            Reporter: Uwe L. Korn
>            Priority: Major
>             Fix For: 0.13.0
>
>
> Now that we have an Arrow homebrew formula again and we may want to have it 
> as a simple setup for R Arrow users, we should add a nightly crossbow task 
> that checks whether this still builds fine.
> To implement this, one should write a new travis.yml like 
> [https://github.com/apache/arrow/blob/master/dev/tasks/python-wheels/travis.osx.yml]
>  that calls {{brew install apache-arrow --HEAD}}. This task should then be 
> added to https://github.com/apache/arrow/blob/master/dev/tasks/tests.yml so 
> that it is executed as part of the nightly chain.



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

Reply via email to