This page is in its very early life, consider this higly work-in-progress

Continuous Integration and Quality Assurance for Gluster in the Storage SIG

We're a diverse team that uses the Jenkins infrastructure from the CentOS CI. The different tests can be found in our (to be created) Jenkins Job Builder repository.

There are two ways in the CentOS CI how Gluster gets tested:

1. Storage SIG contents
2. upstream Gluster development

For communication we use (undecided) gluster-devel@gluster.org, centos-devel@centos.org, ci-users@centos.org. You can find most of us in the #centos-devel IRC channel on Libera Chat.

1. Team Members

New members can request access to the CenOS CI through these bugs:

• account request for testing CentOS Storage SIG packages

• account request for upstream Gluster development testing

2. Available Tests

... too few!

3. Planned Tests

3.1. Storage SIG packages

• nightly installation with most recent CentOS updates
• alpha/beta/pre-release testing
• ...

3.2. Upstream Gluster Development

• DiSTAF

• (possibly) regression testing when patches for upstream gluster are sent to Gerrit

• nightly tests
• ...

4. Test Ownership and Maintenance

4.1. Storage SIG packages

4.2. Upstream Gluster Development

All Jenkins jobs should start their name with 'gluster' so that they get listed in the Upstream Gluster view. The actual scripts and Jenkins jobs (.xml files) that run in the CI are maintained in the Gluster patch acceptance tests repository.