sjperkins commented on PR #33805:
URL: https://github.com/apache/arrow/pull/33805#issuecomment-1399230496

   > > Could you also add entries for this to 
https://github.com/apache/arrow/blob/master/dev/tasks/tasks.yml#L455-L465 ?
   > 
   > I've done so, but I'm not sure how to test correctness locally. This seems 
to be part of the crossbow archery component which kicks off nightly CI 
services which I'm fairly certain I don't have permissions for.
   > 
   > > Crossbow is a subcomponent of Archery and can be used to manually 
trigger builds.  The tasks which can be run on Crossbow can be found in the 
`dev/tasks` directory.  This directory contains:
   > 
   > > * the file `dev/tasks/tasks.yml` containing the configuration for 
various tasks which can be run via Crossbow
   > > * subdirectories containing different task templates (specified using 
`jinja2 syntax <https://jinja.palletsprojects.com/>`_), divided roughly by 
language or package management system.
   > 
   > > Most of these tasks are run as part of the nightly builds, though they 
can also be triggered manually by add a comment to a PR which begins with 
`@github-actions crossbow submit` followed by the name of the task to be run.
   > 
   > > For convenience purpose, the tasks in `dev/tasks/tasks.yml` are defined 
in groups, which makes it simpler for multiple tasks to be submitted to 
Crossbow at once.  The task definitions here contain information about which 
service defined in `docker-compose.yml` to run, the CI service to run the task 
on, and which template file to use as the basis for that task.
   
   I see this started CI and related tests which revealed issues, addressed in 
https://github.com/apache/arrow/pull/33805/commits/424fa0802b314a273ddc1f449d9e5e633b8c4804.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to