kou commented on issue #46014: URL: https://github.com/apache/arrow/issues/46014#issuecomment-2788116003
> What if the apache/arrow GHA capacity decreases? I'm not sure what is our current concurrency limit. https://infra.apache.org/github-actions-policy.html has the following: ```quote * The average number of minutes a project uses per calendar week MUST NOT exceed the equivalent of 25 full-time runners (250,000 minutes, or 4,200 hours). * The average number of minutes a project uses in any consecutive five-day period MUST NOT exceed the equivalent of 30 full-time runners (216,000 minutes, or 3,600 hours). ``` 2025-04-01/2025-04-08 statistics: https://github.com/apache/arrow/actions/metrics/usage?dateRangeType=DATE_RANGE_TYPE_CUSTOM&range=1743465600000-1744070400000 Total minutes: 77,900 > Are there crossbow jobs running on other CI systems which couldn't be ported? Currently, we only use GitHub Actions and Azure Pipelines. So we'll be able to port all jobs to GitHub Actions. > What if we need to support non-github hosted architectures? We would solve it using self-hosted runners? We'll try self-hosted runners or we mark these architectures as tier 2 or tier 3 platforms. See also: https://github.com/apache/arrow/issues/46002 > In an ideal setup we could easily create a release by: > > 1. pressing a button, triggering jobs, uploading artifacts using https://github.com/actions/upload-artifact? > 2. notifying the release manager or dev@ that the artifacts are available > 3. release manager downloads, signs and uploads the artifacts under the release tag? > 4. trigger the post-release tasks (wherever additional credentials are not required or machine tokens could be used) I hope that `git tag && git push` can trigger all of them (build source archive, sign it, upload it, build binary artifacts from it, sign them, upload them, verify them, start a vote, ...) with [Automated Release Signing](https://infra.apache.org/release-signing.html#automated-release-signing). :-) -- 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: github-unsubscr...@arrow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
