-
Notifications
You must be signed in to change notification settings - Fork 325
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
plugin(jenkins-backend): Add extension point #3000
base: main
Are you sure you want to change the base?
Conversation
Add an extension point to the `jenkins-backend` plugin so a custom JenkinsInforProvider can be used. Fixes backstage#2926 Signed-off-by: Luiz Carvalho <[email protected]>
Changed Packages
|
Yes it looks good. Thanks for the effort |
Anything else that needs to be done before this change is reviewed and, eventually, merged? |
@04kash @BethGriggs another Jenkins PR |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @lcarva! The docs would need to be updated on how to provide a custom JenkinsInfoProvider using this new extension point as well. You can take a look at the keycloak docs and the badges docs for examples.
} | ||
|
||
/** | ||
* Extension point that allows a different JenkinsInfoProvider to be used. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
* Extension point that allows a different JenkinsInfoProvider to be used. | |
* Extension point that allows a custom JenkinsInfoProvider to be used. |
Hey, I just made a Pull Request!
Add an extension point to the
jenkins-backend
plugin so a custom JenkinsInforProvider can be used.✔️ Checklist
Signed-off-by
line in the message. (more info)