Non-responsive maintainer

[Greg Hellings]

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

--Greg

[Fabio Valentini]

On Thu, Aug 29, 2019 at 7:51 PM Greg Hellings <greg.hellings(a)gmail.com&gt; 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).

Fabio

> --Greg
> _______________________________________________
> devel mailing list -- devel(a)lists.fedoraproject.org
> To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
> 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/[e-mail]

[John Harris]

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(a)gmail.com&gt;
>  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(a)splentity.com&gt;
Splentity
https://splentity.com/

[Nico Kadel-Garcia]

Jenkins in a container is begging for container churn with artifacts and logs. Jenkins
*slaves* are another story,

Sent from my iPhone

> On Aug 29, 2019, at 9:38 PM, John Harris <johnmh(a)splentity.com&gt; wrote:
> 
>> 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(a)gmail.com&gt;
>> 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(a)splentity.com&gt;
> Splentity
> https://splentity.com/
> 
> _______________________________________________
> devel mailing list -- devel(a)lists.fedoraproject.org
> To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
> 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/[e-mail]