[
https://issues.apache.org/jira/browse/HBASE-30522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18139135#comment-18139135
]
Charles Connell commented on HBASE-30522:
-----------------------------------------
Thanks Kevin. I think the resource limit on Github that would be most worrying
is probably the [total concurrent
jobs|https://docs.github.com/en/actions/reference/limits#job-concurrency-limits-for-github-hosted-runners],
which is 1000 for the ASF's Enterprise plan. This limit applies across all
Apache projects together. I just realized this after looking into it based off
Duo's email.
I don't think any other limits are realistically a problem, and actually the
Github runners are so much faster than the Jenkins boxes, so it's a big
improvement in some ways.
> Discuss whether Jenkins tests should be migrated to GitHub Actions
> ------------------------------------------------------------------
>
> Key: HBASE-30522
> URL: https://issues.apache.org/jira/browse/HBASE-30522
> Project: HBase
> Issue Type: Brainstorming
> Components: integration tests, test
> Reporter: Kevin Geiszler
> Priority: Major
>
> We currently run tests using both Jenkins and GitHub Actions. Jenkins is
> used to nightly test runs, and GitHub Actions are used for validating builds
> for pull requests.
> An email regarding HBASE-30087 was sent to the dev list recently, and there
> was some discussion on these tests being run with Jenkins versus GitHub
> Actions, with available resources being the main concern for adding more
> tests to GitHub Actions. It may be useful to continue that discussion here.
> These are some initial question I have:
> * What's the amount of available resources on GitHub Actions?
> * Can this amount be feasibly increased to accommodate for moving all
> Jenkins tests to GHA?
> * Does moving everything to one place (GHA) provide enough of a benefit?
> Any other questions/thoughts/comments are welcomed as well.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
