[JIRA] (JENKINS-42502) blueocean dependencies do not seem to be optional - causing the whole UI to break

2019-08-28 Thread jn...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Nord commented on  JENKINS-42502  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: blueocean dependencies do not seem to be optional - causing the whole UI to break   
 

  
 
 
 
 

 
 I believe (not validated) that certain blueocean plugins can now be uninstalled.  You should not need the blueOcean aggregator and from then on  you can uninstall the blueocean-Jira plugin. Note you will have to maintain all of the blueocean plugins at the same version manually from then on.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.179429.1488815363000.2231.1567010220171%40Atlassian.JIRA.


[JIRA] (JENKINS-42502) blueocean dependencies do not seem to be optional - causing the whole UI to break

2019-08-28 Thread has...@free.fr (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Antoine Musso commented on  JENKINS-42502  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: blueocean dependencies do not seem to be optional - causing the whole UI to break   
 

  
 
 
 
 

 
 I have a use case. Blue Ocean depends on a lot of plugins which would get security updates from time to time. Whenever one of those plugins is hit by a security update, we have to update our Jenkins installations even though we have no use for the plugins. Though I get the intent that if one installs the Jira plugin, the Blue Ocean integration should be installed as well. In our case we do not use Jira at all and would thus happily dispose of both Jira and the related integration plugins.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.179429.1488815363000.2227.1567009920201%40Atlassian.JIRA.


[JIRA] (JENKINS-42502) blueocean dependencies do not seem to be optional - causing the whole UI to break

2017-03-09 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay resolved as Won't Fix  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 You are right - they are not optional and this is intentional for us to deliver a consistent Blue Ocean experience thats the same for everyone. Blue Ocean is a product experience not a plugin. If you do have a use case for removing certain plugins that I am not aware of please let us know. "You can be watching TV and see Coca-Cola, and you know that the President drinks Coke, Liz Taylor drinks Coke, and just think, you can drink Coke, too. A Coke is a Coke and no amount of money can get you a better Coke than the one the bum on the corner is drinking. All the Cokes are the same and all the Cokes are good." – Andy Warhol   
 

  
 
 
 
 

 
 Jenkins /  JENKINS-42502  
 
 
  blueocean dependencies do not seem to be optional - causing the whole UI to break   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Won't Fix  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   

[JIRA] (JENKINS-42502) blueocean dependencies do not seem to be optional - causing the whole UI to break

2017-03-06 Thread jn...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Nord updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42502  
 
 
  blueocean dependencies do not seem to be optional - causing the whole UI to break   
 

  
 
 
 
 

 
Change By: 
 James Nord  
 

  
 
 
 
 

 
 A failed BO plugin  dependency  barfs all of blue ocean. Extensions to the main BO plugin should be optional for a multitude of reasons and should not barf all of the UI. 1) not to barf on a single plugin failure2) not to require the entire list of plugins to be installed form the update site (hey I do not use github so I don't want that installed - ever...){noformat}SEVERE: Failed Loading plugin Pipeline: GitHub Groovy Libraries v1.0 (pipeline-github-lib)java.io.IOException: Pipeline: GitHub Groovy Libraries v1.0 failed to load.- Pipeline: Shared Groovy Libraries v2.3 is older than required. To fix, install v2.5 or later.at hudson.PluginWrapper.resolvePluginDependencies(PluginWrapper.java:621)at hudson.PluginManager$2$1$1.run(PluginManager.java:516)at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169)at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282)at jenkins.model.Jenkins$7.runTask(Jenkins.java:1086)at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210)at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117)at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)at java.lang.Thread.run(Thread.java:745)Mar 06, 2017 3:07:29 PM jenkins.InitReactorRunner$1 onTaskFailedSEVERE: Failed Loading plugin GitHub Organization Folder Plugin v1.6 (github-organization-folder)java.io.IOException: GitHub Organization Folder Plugin v1.6 failed to load.- Pipeline: GitHub Groovy Libraries v1.0 failed to load. Fix this plugin first.at hudson.PluginWrapper.resolvePluginDependencies(PluginWrapper.java:621)at hudson.PluginManager$2$1$1.run(PluginManager.java:516)at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169)at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282)at jenkins.model.Jenkins$7.runTask(Jenkins.java:1086)at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210)at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117)at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)at java.lang.Thread.run(Thread.java:745)Mar 06, 2017 3:07:29 PM jenkins.InitReactorRunner$1 onTaskFailedSEVERE: Failed Loading plugin GitHub Pipeline for Blue Ocean v1.0.0-b24 (blueocean-github-pipeline)java.io.IOException: GitHub Pipeline for Blue Ocean v1.0.0-b24 failed to load.- GitHub Organization Folder Plugin v1.6 failed to load. Fix this plugin first.at hudson.PluginWrapper.resolvePluginDependencies(PluginWrapper.java:621)at hudson.PluginManager$2$1$1.run(PluginManager.java:516)at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169)at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282)at 

[JIRA] (JENKINS-42502) blueocean dependencies do not seem to be optional - causing the whole UI to break

2017-03-06 Thread jn...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Nord created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42502  
 
 
  blueocean dependencies do not seem to be optional - causing the whole UI to break   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 blueocean-plugin  
 
 
Created: 
 2017/Mar/06 3:49 PM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 James Nord  
 

  
 
 
 
 

 
 A failed BO plugin barfs all of blue ocean.   Extensions to the main BO plugin should be optional for a multitude of reasons and should not barf all of the UI.   1) not to barf on a single plugin failure 2) not to require the entire list of plugins to be installed form the update site (hey I do not use github so I don't want that installed - ever...) 

 
SEVERE: Failed Loading plugin Pipeline: GitHub Groovy Libraries v1.0 (pipeline-github-lib)
java.io.IOException: Pipeline: GitHub Groovy Libraries v1.0 failed to load.
- Pipeline: Shared Groovy Libraries v2.3 is older than required. To fix, install v2.5 or later.
at hudson.PluginWrapper.resolvePluginDependencies(PluginWrapper.java:621)
at hudson.PluginManager$2$1$1.run(PluginManager.java:516)
at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169)
at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282)
at jenkins.model.Jenkins$7.runTask(Jenkins.java:1086)
at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210)
at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)

Mar 06, 2017 3:07:29 PM jenkins.InitReactorRunner$1 onTaskFailed
SEVERE: Failed Loading plugin GitHub Organization Folder Plugin v1.6 (github-organization-folder)
java.io.IOException: GitHub Organization Folder Plugin v1.6 failed to load.
- Pipeline: 

[JIRA] (JENKINS-42502) blueocean dependencies do not seem to be optional - causing the whole UI to break

2017-03-06 Thread jn...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Nord updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42502  
 
 
  blueocean dependencies do not seem to be optional - causing the whole UI to break   
 

  
 
 
 
 

 
Change By: 
 James Nord  
 
 
Priority: 
 Minor Major  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.