raulcd commented on issue #46014: URL: https://github.com/apache/arrow/issues/46014#issuecomment-3285359673
I've been doing some numbers. We have 241 jobs spread between workflows on the `apache/arrow` repository and tasks on `ursacomputing/crossbow`: `apache/arrow`: - 39 from GitHub actions + 1 from Appveyor `ursacomputing/crossbow`: - 34 release tasks - 61 packaging tasks - 81 test tasks - 5 tasks not being exercised on nightlies If we use the following tags as a target to move the crossbow tasks we would have: - `CI Extra: cpp` --> 19 jobs - `CI Extra: python` --> 26 jobs - `CI Extra: cglib-ruby` --> 4 jobs - `CI Extra: r` --> 27 jobs - `CI Extra: linux-packaging` --> 21 jobs - `CI Extra: wheels` --> 36 jobs - `CI Extra: release` --> 34 jobs (verification tasks) There are some questions, what do we want to do with the ursacomputing tasks that are not part of the nightly jobs: - matlab - r-recheck-strong - r-recheck-most - test-debian-experimental-cpp-gcc-15 - preview-docs The preview-docs is slightly different and we can ignore it at the moment. There are also some tasks that I am unsure where would fit on that label proposal (and haven't been added to those totals): - homebrew-cpp - conan-maximum - conan-minimum - test-build-vcpkg-win - r-binary-packages (directly on r?) - test-debian-12-docs - test-cuda-cpp-ubuntu-22.04-cuda-11.7.1 - test-cuda-python-ubuntu-22.04-cuda-11.7.1 The numbers for some of the tasks are still quite big, having to run 36 jobs every time I add the `CI Extra: wheels` or 21 for `CI Extra: linux-packaging` is a lot when I might be validating a fix and want a single job to run. -- 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]
