Testing Farm stores all test artifacts in its Artifacts Storage service. Currently there are two deployments of the artifacts storage.
Available via https://artifacts.dev.testing-farm.io
Retention time: 90 days
Red Hat Ranch
Available via https://artifacts.osci.redhat.com/testing-farm
Retention time: unlimited
Directory index is not provided here, append
Testing Farm provides an easy way how to access reports for cloud costs per Testing Farm user.
This feature is available only for Red Hat employees using 🎩 Red Hat ranch. For Public ranch, the feature is currently not planned.
The cloud costs are being reported only for AWS.
The cloud costs reporting is available via AWS web console.
Logging into AWS
Logging in is required in order to access the cloud cost dashboard.
All employees working in PnT have read-only access to the AWS Cost Explorer. To log in, use the following link.
In case you already have access to AWS, you need to choose the following role:
Account: arr-cloud-aws-core (727920394381) Role: 727920394381-cloud-costs
Sign in button.
Accessing Testing Farm Costs Dashboard
To access the dashboard, use the following link.
BaseOS CI costs are not included in the report. If you are interested in BaseOS CI report, see the following link.
By default, the dashboard is showing the cloud spend for the last 7 days.
To change the reporting date range, use the
Report Parameters → Time → Date Range on the right side.
To see the cloud costs per team, use the
Cost and usage breakdown on the bottom.
Changing the Team Name
In case you are using Packit service, it is advised to explicitly define the team name for the reporting. By default, the costs will be reported against Packit service, which interacts with Testing Farm.
See the Packit configuration example - Tag cloud resources in Testing Farm for details.