Retriggering

You can retrigger CI jobs in dist-git pull requests by posting comments that include the appropriate /packit-ci commands, as outlined below.

Help

Packit is able to provide a help message summarizing all available commands and options:

/packit-ci help

Scratch builds

To retrigger a scratch build, add the following comment to the pull request:

/packit-ci scratch-build

Only packagers can retrigger scratch builds.

Tests

To retrigger all tests, add the following comment to the pull request:

/packit-ci test

To retrigger a specific test, you can add the test identifier to the command:

/packit-ci test installability

Currently supported identifiers are:

• installability - represents the Installability test
• rpmlint - represents the rpmlint test
• rpminspect - represents the rpminspect test
• custom - represents Custom TMT test plans

Only packagers can retrigger tests.

Check target

By default, when (re)triggering jobs in rawhide PRs of ELN packages, jobs are run for both the eln and rawhide targets when no dedicated eln branch exists. It is possible to specify which jobs to retrigger with an additional keyword argument --target like so:

/packit-ci test --target eln
/packit-ci test rpminspect --target rawhide
/packit-ci scratch-build --target eln