Initial commit

This commit is contained in:
Cristian Le 2026-02-10 17:45:17 +01:00
commit 3d206307a6
9 changed files with 98 additions and 0 deletions

1
.env Normal file
View file

@ -0,0 +1 @@
KOJI_TASK_ID=123014869

1
.fmf/version Normal file
View file

@ -0,0 +1 @@
1

47
CONTRIBUTING.md Normal file
View file

@ -0,0 +1,47 @@
# Contribution guide
## How to add new shared tests
Simply add a new tmt plan using [`plan.import`], under a new folder. If the
plan is still under development, consider gating it by the `deployment` context
```yaml
plan:
import:
url: ...
name: ...
enable: false
adjust:
when: deployment == stg
```
## Designing the actual plan
The following are a few requirements and guidelines we recommend for the tmt
plan implementations.
### Specify the `provision` step
This is **REQUIRED**. Testing-farm is called without a `compose` in order to
allow plans that use a custom `provision` step, e.g. to run under a specific
container.
### Control the tests via `context` and `environment` variables
The `context` and `environment` variables are defined in [TMT Integration]
page. Consult that page for the expected variables and their meanings. These
variables define the test environment and the package to be tested.
### Document any additional variables the plan **may** use
You are free to define any additional `context` and `environment` variables as
long as there is a default behavior if these were not provided.
### Use `tests` as steps for the actual test
In order to make the plan results more navigable, consider splitting the test
execution into multiple ordered tests as individual steps.
[`plan.import`]: https://tmt.readthedocs.io/en/stable/spec/plans.html#import-plans
[TMT Integration]: https://packit.dev/fedora-ci/tmt-integration

25
README.md Normal file
View file

@ -0,0 +1,25 @@
# Fedora CI shared tests
TMT tests that are run on Fedora CI for each package.
This repo is composed of the references to the tmt plans that are being run.
Navigate to the plans that are being imported for the actual implementations.
## How to test locally
TMT tests are designed to be runnable locally with "minimal" input specifying
what and how to test. These are passed via `context` and `environment`
variables.
```shell
$ tmt -c @context.yaml run -e @.env plans --name /rpminspect
```
This command takes the `context` and `environment` variables from the files
`context.yaml` and `.env` present in this repository. These files are only for
reference, please edit them accordingly to point to the actual package you want
to test. See the [TMT Integration] document for more details on the values that
these variables should have. Each plan may have additional control parameters,
see the actual plans implementations for more detail.
[TMT Integration]: https://packit.dev/fedora-ci/tmt-integration

7
context.yaml Normal file
View file

@ -0,0 +1,7 @@
# Fixed context always defined in Fedora CI runs
initiator: fedora-ci
trigger: commit # TODO: move this when Packit Fedora CI runs on bodhi update
# Variable context which can
arch: x86_64
dist-git-branch: rawhide
distro: fedora-rawhide

4
installability/main.fmf Normal file
View file

@ -0,0 +1,4 @@
plan:
import:
url: https://github.com/fedora-ci/installability-pipeline.git
name: /installability

5
main.fmf Normal file
View file

@ -0,0 +1,5 @@
enabled: false
adjust:
when: deployment == stg
enabled: true
because: Shared tests are still under development

4
rpminspect/main.fmf Normal file
View file

@ -0,0 +1,4 @@
plan:
import:
url: https://github.com/fedora-ci/rpminspect-pipeline.git
name: /rpminspect

4
rpmlint/main.fmf Normal file
View file

@ -0,0 +1,4 @@
plan:
import:
url: https://github.com/packit/tmt-plans.git
name: /plans/rpmlint