Kayode dev #1063
Open
Kayode dev #1063
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Build succeeded. ✔️ pre-commit SUCCESS in 1m 09s |
mfocko
reviewed
Sep 16, 2025
docs/cli/test.md
Outdated
|
|
||
| # `packit test` | ||
|
|
||
| Run TMT tests locally using content from the upstream repository, mimicking the behavior of the tmt functionality. |
There was a problem hiding this comment.
Suggested change
| Run TMT tests locally using content from the upstream repository, mimicking the behavior of the tmt functionality. | |
| Run tmt tests locally using content from the upstream repository, mimicking the behavior of the tmt functionality. |
docs/cli/test.md
Outdated
|
|
||
| Run TMT tests locally using content from the upstream repository, mimicking the behavior of the tmt functionality. | ||
|
|
||
| By default, (if no rpm paths are passed), packit builds RPMs from the current repository's spirce code using Mock, then runs TMT tests in a container environment. This enables local debugging and iteration without requiring commits or CI pipeline triggers. |
There was a problem hiding this comment.
Suggested change
| By default, (if no rpm paths are passed), packit builds RPMs from the current repository's spirce code using Mock, then runs TMT tests in a container environment. This enables local debugging and iteration without requiring commits or CI pipeline triggers. | |
| By default, if no RPM paths are passed, packit builds RPMs from the current repository's source code using `mock`, then runs tmt tests in a container environment. This enables local debugging and iteration without requiring commits or CI pipeline triggers. |
docs/cli/test.md
Outdated
|
|
||
| By default, (if no rpm paths are passed), packit builds RPMs from the current repository's spirce code using Mock, then runs TMT tests in a container environment. This enables local debugging and iteration without requiring commits or CI pipeline triggers. | ||
|
|
||
| You can override test behavior and build configuration directly from the command line using various options like --target, --plans, --rpm-paths, and --clean-before/--no-clean-before. |
There was a problem hiding this comment.
Suggested change
| You can override test behavior and build configuration directly from the command line using various options like --target, --plans, --rpm-paths, and --clean-before/--no-clean-before. | |
| You can override test behavior and build configuration directly from the command line using various options like `--target`, `--plans`, `--rpm-paths`, and `--clean-before`/`--no-clean-before`. |
docs/cli/test.md
Outdated
|
|
||
| The command supports two main workflows: | ||
|
|
||
| - Auto-build workflow: Build RPMs from source code and run tmt tests on the built rpm. This is trggered when there's no --rpm_paths passed via the cli. |
There was a problem hiding this comment.
Suggested change
| - Auto-build workflow: Build RPMs from source code and run tmt tests on the built rpm. This is trggered when there's no --rpm_paths passed via the cli. | |
| - Auto-build workflow: Build RPMs from source code and run tmt tests on the built RPM. This is triggered when there's no `--rpm-paths` passed via the CLI. |
docs/cli/test.md
Outdated
| The command supports two main workflows: | ||
|
|
||
| - Auto-build workflow: Build RPMs from source code and run tmt tests on the built rpm. This is trggered when there's no --rpm_paths passed via the cli. | ||
| - Pre-built RPM workflow: Test existing RPM files, Paths to the rpm(s) are passed with the `--rpm_paths` option. |
There was a problem hiding this comment.
Suggested change
| - Pre-built RPM workflow: Test existing RPM files, Paths to the rpm(s) are passed with the `--rpm_paths` option. | |
| - Pre-built RPM workflow: Test existing RPM files, Paths to the RPMs are passed with the `--rpm-paths` option. |
docs/cli/test.md
Outdated
|
|
||
| * Upstream project is using git. | ||
| * Packit config file placed in the upstream repository. | ||
| * TMT (Test Management Tool) available in the system. |
There was a problem hiding this comment.
Suggested change
| * TMT (Test Management Tool) available in the system. | |
| * `tmt` (Test Management Tool) available in the system. |
docs/cli/test.md
Outdated
|
|
||
| ## Tutorial | ||
|
|
||
| 1. Place a config file for packit in the root of your upstream repository... |
There was a problem hiding this comment.
Suggested change
| 1. Place a config file for packit in the root of your upstream repository... | |
| 1. Place a config file for packit in the root of your upstream repository. |
|
Hi @mfocko , I've made the changes |
|
Build succeeded. ✔️ pre-commit SUCCESS in 1m 19s |
majamassarini
approved these changes
Oct 3, 2025
|
|
||
| The command supports two main workflows: | ||
|
|
||
| - Auto-build workflow: Build RPMs from source code and run tmt tests on the built RPM. This is triggered when there's no `--rpm-paths` passed via the CLI. |
There was a problem hiding this comment.
Suggested change
| - Auto-build workflow: Build RPMs from source code and run tmt tests on the built RPM. This is triggered when there's no `--rpm-paths` passed via the CLI. | |
| - Auto-build workflow: build RPMs from source code and run tmt tests on the built RPM. This is triggered when there's no `--rpm-paths` passed via the CLI. |
| The command supports two main workflows: | ||
|
|
||
| - Auto-build workflow: Build RPMs from source code and run tmt tests on the built RPM. This is triggered when there's no `--rpm-paths` passed via the CLI. | ||
| - Pre-built RPM workflow: Test existing RPM files, Paths to the RPMs are passed with the `--rpm-paths` option. |
There was a problem hiding this comment.
Suggested change
| - Pre-built RPM workflow: Test existing RPM files, Paths to the RPMs are passed with the `--rpm-paths` option. | |
| - Pre-built RPM workflow: test existing RPM files, Paths to the RPMs are passed with the `--rpm-paths` option. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Documentation for packit test command
Fixes
Related to
Merge before/after
RELEASE NOTES BEGIN
Packit now supports automatic ordering of ☕ after all checks pass.
RELEASE NOTES END