On Wed, May 24, 2023 at 2:50 PM Ullrich Hafner <ullrich.haf...@gmail.com> wrote: > Popper is now part of the Bootstrap plugin.
Yes, jenkinsci/bootstrap5-api-plugin@76fd031d8291a9a836264c34b630c8c273102c86 resolves the issue from my perspective. On Wed, May 24, 2023 at 2:46 PM Ullrich Hafner <ullrich.haf...@gmail.com> wrote: > I understand that this is the best thing from an architectural view. But > sometimes you need to make tradeoffs otherwise development costs will > increase too much… The development costs of committing to support a third-party API in perpetuity are prohibitively expensive. But I understand the frustration — maintaining library plugins is not a lot of fun. You could gain back development velocity (at the cost of efficiency) by using the static linking approach (typically with Webpack) practiced by e.g. azure-ad, pipeline-graph-view, workflow-cps, etc. That seems to be the way the Golang and Rust communities have evolved, despite the inefficiency. Unfortunately maintaining a correct and efficient dynamically-linked system is just a huge amount of work, as demonstrated by the constant effort that is needed to build and package software for operating system distributions. The only thing I can think of that would make this easier for you would be better documentation to hopefully inspire others to assist with the burden of maintaining JavaScript Jenkins library plugins. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAFwNDjo51aHobd_Oswkika%2BwxB6kSB%3DqsMdS1yorKx59HwB06Q%40mail.gmail.com.
