🐛 Jenkins: No way to configure JenkinsInfoProvider #2926
Labels
Comments
|
yep, it looks like an extension point is missing. Marked as help wanted |
lcarva
added a commit
to lcarva/backstage-community-plugins
that referenced
this issue
Feb 26, 2025
Add an extension point to the `jenkins-backend` plugin so a custom JenkinsInforProvider can be used. Fixes backstage#2926 Signed-off-by: Luiz Carvalho <lucarval@redhat.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Workspace
jenkins
📜 Description
We've been using the Jenkins plugin with a custom JenkinsInfoProvider implementation through the createRouter function for a wile. After the latest changes in the plugin, the createRouter is no longer exported, but there is now plugin extension point to allow us to provide our custom implementation.
As i could check from the plugin code, the JenkinsInfoProvider is hardcoded inside the plugin initialiser and there is no way to supply i bespoke version as documented. By the way the plugin doc might be missing info on how to set this up.
👍 Expected behavior
Since this capability is already there, i would propose creating an extension point for the InfoProvider to allow users to override the default one.
👎 Actual Behavior with Screenshots
👟 Reproduction steps
No need
📃 Provide the context for the Bug.
No response
👀 Have you spent some time to check if this bug has been raised before?
🏢 Have you read the Code of Conduct?
Are you willing to submit PR?
None
The text was updated successfully, but these errors were encountered: