Hi Roland, Ulli summarized the situation very well.
If you can consider providing a more specific list of plugins that you're waiting on, we can probably point you to the right path to get them fixed (become maintainer, pay someone to fix them, etc.). (very personal) rule of thumb: if the plugin has less than ~2 to 3k installs worldwide, there's close to zero chance that somebody steps up if you do not. Cheers Le ven. 4 juin 2021 à 13:44, Ullrich Hafner <ullrich.haf...@gmail.com> a écrit : > Am 04.06.2021 um 12:51 schrieb Roland Asmann <roland.asm...@gmail.com>: > > > Hi all, > > Because of the table-to-div changes in 2.277.1 not working in several > plugins, I am still running 2.263.4. Every time I check the list of known > plugins that aren't working since this update, the list seems to grow... > A different change in Jenkins a couple of years back made us setup a > second Jenkins instance, because of projects that weren't able run on the > new version. I am still migrating some of those projects and I really don't > want to setup a 3rd instance and maintain all 3. > > So, how do I proceed? Can someone 'force' the plugin developers to update > their plugins? > > > No. If a plugin does not yet support 2.277.1 then the plugin is probably > not maintained at all anymore. Then it would help if someone who still uses > the plugin would volunteer to take over the ownership. This is how our open > source model in Jenkins works. > > Or maybe someone can look some of the plugins over and get them running > again? > > > See above. We do not have a support policy for plugins, so if something > does not work and the maintainer has no spare time to fix then it is up to > the community to help here. > > And maybe it would be good if someone could check over all open issues in > this list ( > https://issues.jenkins.io/secure/Dashboard.jspa?selectPageId=20741) and > see if they are actually still existing/are referencing the correct plugin > -- some issues were created saying it was an issue in the core, but the > comments later state it was actually a plugin. I really need to know if > there are still issues in the core or if it's only in some plugins, so I > can decide on how to move on... > > Thanks. > > Roland > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/ff4acd22-e8c5-4dc7-8284-645c5c1375d6n%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-users/ff4acd22-e8c5-4dc7-8284-645c5c1375d6n%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/C6997362-A032-4300-B131-9E70A953CDE5%40gmail.com > <https://groups.google.com/d/msgid/jenkinsci-users/C6997362-A032-4300-B131-9E70A953CDE5%40gmail.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CANWgJS7_rqvdRagHHmBHy%3DVU2185ZDJMZ6qhpjC7R6%3DnhbhcMg%40mail.gmail.com.
