[Release] Run binary RC verification jobs in apache/arrow #45675
Comments
|
+1 we have enough CI capacity for it (we could pull over even more crossbow jobs actually) but these are only run for the release, so no problem at all. |
kou
added a commit
to kou/arrow
that referenced
this issue
Mar 7, 2025
kou
added a commit
to kou/arrow
that referenced
this issue
Mar 7, 2025
kou
added a commit
to kou/arrow
that referenced
this issue
Mar 7, 2025
raulcd
pushed a commit
that referenced
this issue
Mar 10, 2025
…45699) ### Rationale for this change We don't need to run binary RC verification jobs by Crossbow because they are only used when we release RC. So they are not heavy for us. ### What changes are included in this PR? Move binary RC verification jobs to `.github/workflows/verify_rc.yml` from `dev/tasks/` ### Are these changes tested? Yes. ### Are there any user-facing changes? No. * GitHub Issue: #45675 Authored-by: Sutou Kouhei <kou@clear-code.com> Signed-off-by: Raúl Cumplido <raulcumplido@gmail.com>
|
Issue resolved by pull request 45699 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the enhancement requested
This is for #45548.
Currently, binary RC verification jobs are run in ursacomputing/crossbow via
dev/tasks/tasks.ymland Crossbow. But we don't need to use Crossbow for them because we can't run them nightly.If we use apache/arrow not ursacomputing/crossbow, we can implement #45548 easily.
Component(s)
Release
The text was updated successfully, but these errors were encountered: