[
https://issues.apache.org/jira/browse/HBASE-30522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18146319#comment-18146319
]
Kevin Geiszler commented on HBASE-30522:
----------------------------------------
Yes, GitHub works well, and the HBase Jenkins CI has been slow/not working
consistently the past couple of months. Is there any way to see the total
number of GitHub actions jobs used by Apache right now? Idk how keen they would
be on paying more to increase the resource limit
> 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)