For nightly builds we are still on jenkins and we have some dedicated
resources for jenkins builds.

On github actions, we have already consumed a lot of resources so we'd
better not add more loads on it, especially periodical tests...

Charles Connell via dev <[email protected]> 于2026年10月27日周二 07:52写道:
>
> Hi Kevin,
>
> The new tests are good thing. I think Github Actions are a better platform
> for builds and integration tests that Jenkins. We moved our PR checks to
> Github Actions because we were able to run them so much faster. Would you
> consider seeing how your tests might work as Github Actions? This might be
> a good way to pilot moving HBase's other nightly automations to Github.
>
> Charles
>
>
> On Mon, Oct 26, 2026 at 2:57 PM Kevin Geiszler via dev <[email protected]>
> wrote:
>
> > Hi everyone,
> >
> > I submitted a pull request to merge feature branch HBASE-30087
> > <https://issues.apache.org/jira/browse/HBASE-30087> into master.  This PR
> > adds Jenkins integration tests for the Read-Replica feature.  Typical HBase
> > mini-clusters cannot be used for testing Read-Replica due to the
> > mini-clusters running in the same JVM, resulting in META_TABLE_NAME
> > conflicts.
> >
> > Instead, these tests run two Docker containers, each acting as an HBase
> > cluster in a Read-Replica setup.  The Jenkins driver script uses Python
> > scripts to run the tests and send commands to each container's HBase
> > shell.  The tests generate a console report similar to what you see in the
> > Nightly Tests.
> >
> > Example Jenkins test runs for HBASE-30087 can be found here:
> > https://ci-hbase.apache.org/job/HBase-Read-Replica-Tests/job/HBASE-30087/
> >
> > Pull request: https://github.com/apache/hbase/pull/8809
> >
> > These tests helped discover bugs during Read-Replica's development phase
> > and will help identify any regressions as future changes are made to
> > HBase.  I am interested in the community's thoughts on this test feature
> > and whether it would be a good addition.
> >
> > Thanks,
> > Kevin Geiszler
> >

Reply via email to