Good Morning Everyone, I while back I wrote a small service named simple-koji-ci, which reacts to every pull-request opened on dist-git and fires a (scratch) build of the package with the proposed changes merged, and report the outcome as a "flag" to the pull-request. This is a very simple service, so simple that it has some issues, including the fact that it uses the default mock configuration to build the SRPM for the scratch build. This can break the SRPM generation in a few cases. This is the very first service we have had triggering of PRs on dist-git and giving some CI feeling/taste to our workflow. Since then, the CI pipeline managed by the Fedora CI SIG folks has appeared, is running and is also doing a scratch build like simple-koji-ci and then some more testing. simple-koji-ci has been running in the openstack instance hosted by the Fedora Infrastructure. However, this openstack is being decommissioned and applications running there are being asked to find another place to run, an option being openshift. I'd like to ask for your input about this service. Is it worth keeping? Is it duplicating what the CI pipeline does? Is someone interested in working on it? If this service is deemed important enough, I don't mind moving it to openshift but in all honestly, what I would prefer would be to help someone move it to openshift. Looking forward to read your thoughts, Thanks, Pierre _______________________________________________ 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
