Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add benefits of using packit to faq #943

Merged
merged 1 commit into from
Oct 4, 2024
Merged

Add benefits of using packit to faq #943

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions docs/faq.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -157,3 +157,14 @@ You can read more about this transition [here](/posts/copr-srpms).
## A command failed in packit-service: how do I reproduce it locally?

Please read [this document on how to reproduce locally](reproduce-locally).

## Why you should use Packit instead of external devices directly?

- Packit uses various services Testing Farm, Copr, Koji, Bodhi…
- These services can be used without Packit, but Packit integrates them in a
more user-friendly way reducing the manual labor that would be required from
the contributor or maintainer. For example:
- the build in Copr is created automatically when a new version is released
- RPMs built by Copr are specifically passed to the Testing Farm for testing
- RPM builds are verified against multiple releases (and also different OSs)
- The user does not have to wait and look for the results but just interprets them.
Loading