Dne 19. 06. 23 v 11:30 Sandro
napsal(a):
2) Even better is Packit
https://packit.dev/
You have many ways to use it. My favorite way is to use pull-from-upstream
https://packit.dev/posts/pull-from-upstream/
You just make sure you have record in https://release-monitoring.org/ and then put .packit.yaml in Fedora's dist-git. And when upstream has a new release you will receive a pull request to src.fedoraproject.org for all configure branches. And when it merges it (can) build in Koji and submit Bodhi update for you.
With Packit you can use full automation or only some steps. And combine it as you like it. If you do not like triggereing by release monitoring, you can initiate it from command line. It is up to you.
Sounds like these tools are worth mentioning in the docs, seeing how many people face the same challenge.
We (I am part of Packit team) plan to do more noise about it
later. Especially this feature - we have finished it in January
and asked few people to try it. We have done several rounds of
fix-and-try-again. Today, we have one outstanding issue "manually
re-trigger event" and I believe that once implemented, it will be
ready for wide audience. If you are brave and ready for bleeding
edge, you can try it now.
-- Miroslav Suchy, RHCA Red Hat, Manager, Packit and CPT, #brno, #fedora-buildsys
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
