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

Nic Crane updated ARROW-13841:
------------------------------
    Description: 
High-level overview:
* Possibly add diagram: 
https://lucid.app/lucidchart/ea221ae9-afc5-4453-8939-970e08759127/edit?shared=true&page=0_0#
* Short description of each component

Specific things to add:
* when you commit to an open PR (e.g. also the automatic scripts we run that 
check the title etc)
* what this workflow is about and why it exists and when runs: 
https://github.com/apache/arrow/blob/master/.github/workflows/cpp_cron.yml
* what happens when we merge a PR (e.g. the dev PR)
* basically, what triggers and when they happen, then once that's documented, 
it makes a lot more sense for people to know what to look at

Generally add more content to make it easier to get started with understanding 
CI.

This section is the relevant location: 
https://github.com/apache/arrow/tree/master/docs/source/developers

Potentially add something about how linx-apt-r (etc) depend on other dockerfiles




  was:
High-level overview:
* Possibly add diagram: 
https://lucid.app/lucidchart/ea221ae9-afc5-4453-8939-970e08759127/edit?shared=true&page=0_0#
* Short description of each component

Specific things to add:
* when you commit to an open PR (e.g. also the automatic scripts we run that 
check the title etc)
* what this workflow is about and why it exists and when runs: 
https://github.com/apache/arrow/blob/master/.github/workflows/cpp_cron.yml
* what happens when we merge a PR (e.g. the dev PR)

Generally add more content to make it easier to get started with understanding 
CI.

This section is the relevant location: 
https://github.com/apache/arrow/tree/master/docs/source/developers

Potentially add something about how linx-apt-r (etc) depend on other dockerfiles





> [Doc] Document the different subcomponents that make up the CI and how they 
> fit together
> ----------------------------------------------------------------------------------------
>
>                 Key: ARROW-13841
>                 URL: https://issues.apache.org/jira/browse/ARROW-13841
>             Project: Apache Arrow
>          Issue Type: Sub-task
>            Reporter: Nic Crane
>            Assignee: Nic Crane
>            Priority: Major
>
> High-level overview:
> * Possibly add diagram: 
> https://lucid.app/lucidchart/ea221ae9-afc5-4453-8939-970e08759127/edit?shared=true&page=0_0#
> * Short description of each component
> Specific things to add:
> * when you commit to an open PR (e.g. also the automatic scripts we run that 
> check the title etc)
> * what this workflow is about and why it exists and when runs: 
> https://github.com/apache/arrow/blob/master/.github/workflows/cpp_cron.yml
> * what happens when we merge a PR (e.g. the dev PR)
> * basically, what triggers and when they happen, then once that's documented, 
> it makes a lot more sense for people to know what to look at
> Generally add more content to make it easier to get started with 
> understanding CI.
> This section is the relevant location: 
> https://github.com/apache/arrow/tree/master/docs/source/developers
> Potentially add something about how linx-apt-r (etc) depend on other 
> dockerfiles



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

Reply via email to