adoption of delivery-pipeline-plugin

[Olivier Schiavo]

Hi,
I would like to adopt a plugin:

    Link: https://github.com/jenkinsci/delivery-pipeline-plugin
    Status: abandonned
    GitHub Username: owengo
    Jenkins Infrastructure ID: owengo
    Repository Permission Updater PR: no idea what it is

We are using the plugin for a longtime and it has no maintainer since 2020.

There was this promising thread early this year:
https://groups.google.com/g/jenkinsci-dev/c/nmNa7HpWKNQ/m/ySIduKgtAwAJ

But we still don't get releases of the plugin with the necessary patches to make it work correctly

Note that I contributed one of the latest merged patch: https://github.com/jenkinsci/delivery-pipeline-plugin/commit/130a8b342a182443420b5e7ca03dc14a66dec3ac

Currently PR 347 on the original repo is not merged into your repo:
https://github.com/Diabol/delivery-pipeline-plugin/pull/347

Which causes an annoying missing image ( the "build now" image actually ). Also breaking changes made on the promotion plugin have been  merged in your repository but no release has been provided by lack of maintainer, cf discussion with Mark E. Waite :
https://github.com/jenkinsci/promoted-builds-plugin/commit/597f5c6ad3fdf4c198401385ef80d7113ff02393

I think the delivery-pipeline-plugin is vastly superior to the "classic" pipeline for many use cases, but it is crippled by the missing merges and the lack of scripting support. Currently I maintain a patched release myself so that we can continue to use the plugin and upgrade regularly jenkins. It will probably not take much more time to directly maintain the original one and everyone would benefit?


Best regards,