class: center, middle
# Packit Workshop --- class: center, middle ![Packit Team](packit-team.png) --- ![Ecosystem](ecosystem.png) --- ![Ecosystem](ecosystem-with-packit.png) --- # Packit * CLI tool ``` $ dnf install packit $ packit --help ``` --- # Packit (cont'd) ``` $ packit status Dist-git versions: f29: 0.4.2 f30: 0.4.2 master: 0.4.2 Latest Bodhi updates: Update Karma status ------------------------------------------- ------- -------- packit-0.4.2-1.fc29 python-ogr-0.5.0-1.fc29 2 stable packit-0.4.2-1.fc30 python-ogr-0.5.0-1.fc30 3 stable packit-0.4.1-1.fc29 3 stable Latest Koji builds: f29: packit-0.4.2-1.fc29 f30: packit-0.4.2-1.fc30 ``` --- # Packit Service * GitHub app --- # Current state (cont'd) ![Packit Service](packit-gh-installation.png) --- # Current state (cont'd)
--- # Current state (cont'd)
--- # Current state (cont'd) https://packit.dev/
--- # FAQ * Do I really need to have a spec file in the upstream repo? -- * Do I need to have your config in the repo? -- * Are we required to use your workflow? --- # What if the upstream devs don't care about Fedora and RPM spec files?
--- # Future steps * On-board as many projects as possible. * Enable building and validating against RHEL. ??? * Meaning: prioritize more generic features --- # Thanks for coming! *
[github.com/TomasTomecek/speaks](https://github.com/TomasTomecek/speaks) *
[github.com/packit-service](https://github.com/packit-service) *
[packit.dev](https://packit.dev/) *
user-cont-team@redhat.com *
user-cont@redhat.com (internal)