On Tue, Jan 7, 2020 at 1:51 PM Miro Hrončok <mhroncok@xxxxxxxxxx> wrote: > > For me, an ultimate success would be if upstream projects would actually use > Fedora-family distros in their CI testing. And I don't mean that they would use > Copr or packit to package RPM packages, or that they deploy their own Jenkins on > CentOS, I mean that they would use something as easy as Travis CI, but instead > of ancient Ubuntu, they could choose from a variety of Fedora systems. Yup, exactly! In packit we're doing it the hard way since we force them to embrace spec files and RPM packaging format. I wouldn't be personally too opposed to an idea where upstream projects could start w/o RPM packaging and just run their tests on Fedora and then, slowly, ramp up to have an RPM package out of their project up to automate release into rawhide. > Unfortunately I don't see this happening without RH partnering up with a major > CI provider or without significant investment in providing our own public CI > (sans RPM) - however we are now discontinuing services, not adding new. We actually had a discussion in December before the break, whether we would enable a workflow in packit that you would not need spec and would be able to test your software directly from the git repo - the same thing as travis or circle does. As far as I recall, the idea is still on the table. Tomas _______________________________________________ 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
