On Thursday, August 29, 2019 11:11:43 AM MST Fabio Valentini wrote: > On Thu, Aug 29, 2019 at 7:51 PM Greg Hellings <greg.hellings@xxxxxxxxx> > wrote: > > > > > > The jenkins pacakge is fearfully out of date and seems unmaintained. Does > > anyone know how to get in touch with the maintainer(s) of the package? > > > > > > > https://bugzilla.redhat.com/show_bug.cgi?id=1560603 > > > It's not only out of date, but also hilariously broken. Just check this > page: https://apps.fedoraproject.org/koschei/search?q=jenkins > > Most of the packaged jenkins plugins have already been retired for > fedora 31+, and jenkins itself is broken because a lot of its > dependencies have been retired as well. > > Judging by the state of the Java stack in fedora, I'd recommend some > kind of container workflow that doesn't actually include fedora > packages for jenkins. > Another approach might be for you to join the Java SIG and revive > jenkins in fedora (which would require a lot of work). I would recommend Jenkins be installed in the vendor supported method. I fail to see how containers would be useful here, but the correct way to do that in a container would be in the method described here: https://fedoramagazine.org/container-technologies-fedora-systemd-nspawn/ -- John M. Harris, Jr. <johnmh@xxxxxxxxxxxxx> Splentity https://splentity.com/ _______________________________________________ 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
