-
Notifications
You must be signed in to change notification settings - Fork 44
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
Remove mandatory install of blue ocean plugin #285
Conversation
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.
what about just making the dependency optional and marking the extension as optional instead?
220a87f
to
ef7c398
Compare
Good idea, I didn't consider that :) |
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.
untested, looks good to me though, thanks!
Rip, can we add a dummy constructor like: public AzureStorageBlueArtifact() {
super(null);
this.action = null;
this.artifact = null;
} or sth else? |
i think so |
I removed the Rest API for Blue Ocean plugin after seeing this update that it was no longer required for the Azure Storage plugin to work. After removing these plugins and restarting Jenkins, I noticed the following errors in our Jenkins system logs. As far as I can tell, everything still works as expected, but seeing these errors in the logs after restart was initially startling:
|
Fixes #278
As a user of the azure-storage plugin who doesn't use BO at all, it's frustrating that I need this dependency installed.
Would you strongly object to removing the BO integration all together @timja?
It was added in 2018 when BO was alive, but 6 years later, it's declared abandoned and EOL. I see no real reason why we should keep up an integration for an end-of-life plugin.