Test Environment

Testing Farm supports a variety of hardware architectures, depending on the ranch being used.

Before Testing Farm starts installing artifacts into the test environment, it adds the EPEL repositories to the system.

Epel repository is added only for CentOS Stream distributions tested via the 🌍 Public ranch.

For RHEL the repository is not added by default, as this is not considered a best practice when testing RHEL.

For enabling the repository for RHEL you can use:

Before Testing Farm starts installing artifacts into the test environment, it adds the "tag repository" to the system. This repository contains all builds tagged with -candidate (i.e. which passed gating) that are not yet present in the nightly repository. It’s currently necessary as landing in nightly can take an indefinite amount of time due to the manual "pre-validation" and "attach to erratum" steps. Adding this repository greatly reduces the number of artifact installation failures.

The repository is auto-generated by the build system - Koji or Brew. The base url of the repository is set up according to the test environment operating system.

Tag repository is added:

Tag repository details:

Testing farm supports a variety of composes, depending on the ranch being used. The lists of composes for every ranch are available below:

When Compose YUM repositories are removed upstream, the composes become almost useless. If you would like to keep a compose for longer than the default time, you will need to request that it be tagged with by ENGCMP with do-not-remove. You will also need to change the keep_until date in variables-composes-yaml. Either request this from Testing Farm team or make a merge request.

This section describes special reserved directories in the testing environment. Your tests should avoid touching these, or unexpected failures can happen.