What about option #3, integrating the extension into the Promoted Builds Plugin? denschu have you contacted the Promoted Build Plugin maintainer(s)? If you get no answer, ask for commit access on the jenkins-dev list and just do it.

daspilker Yes, I created a ticket, but no response: https://issues.jenkins-ci.org/browse/JENKINS-29776
The problem with option #3 is that we have to add Groovy to the codebase of the plugin, which will maybe not accepted by the maintainers of the Promoted Builds plugin...

stevejansen We are actually testing the Extension in a big Jenkins setup with version 1.630. If this works, I'll create a release of it...

denschu OK, but no one objected to add Groovy code in your last dev list thread (https://groups.google.com/forum/#!msg/jenkinsci-dev/IZ3kBFhIYYg/amywuitlHAAJ). I suggest to open a pull request. If no one replied after 2 weeks, ask for commit access on the jenkins-dev list. If you get commit access, integrate your Groovy code into the Promoted Builds Plugin and release the plugin. If not, we need to discuss a viable solution with the maintainer. IMHO, releasing a plugin outside of the Update Center is only a short-term solution.

Guys, any update on this?

Hi,
I created a PR which includes the extension directly into the main promoted-builds-plugin: https://github.com/jenkinsci/promoted-builds-plugin/pull/81
If the PR is merged, we can close this ticket here...

Thanks
Dennis

[edit] removed due to misleading information

The pull request has not been merged yet.

The current PR is https://github.com/jenkinsci/promoted-builds-plugin/pull/82.

Yes, you are right. I have no idea how I have seen it in master branch. My bad

Has been released in Promoted Builds plugin 2.26.