Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-47151

Ability to completely disable the Blue Ocean Pipeline Editor

      Add the ability to disable the Blue Ocean pipeline editor completely.  

      My use-case is that our Jenkins installation does not allow users to create jobs using the UI.  All Jenkinsfiles are located in source control, and jobs get created via github webooks.  

      We want to add Blue Ocean to our installation, but the Blue Ocean pipeline editor is always available and this does not work with our paradigm.

      The request is to add an option to completely disable the Blue Ocean pipeline editor and prevent it from being linked to or shown in the Blue Ocean UI.

      Relevant conversation from gitter:

      Keith Zantow @kzantow 11:32
      @ometa at this point, there's no option for it. however, you could do a hack, by putting a .disabled file in your plugins directory manually (e.g. <jenkins-home>/plugins/blueocean-pipeline-editor.jpi.disabled), then restarting your jenkins instance (it might cause a load failure; haven't tested it)
      (it's just a marker file, no content is necessary)

       

      Apologies if I missed something in this feature request; I will happily update it if so.  Thank you!

          [JENKINS-47151] Ability to completely disable the Blue Ocean Pipeline Editor

          Oops, accidentally changed assignee here, while I wanted to comment on another issue. How comes this is possible for non-devs?

          Dirk Heinrichs added a comment - Oops, accidentally changed assignee here, while I wanted to comment on another issue. How comes this is possible for non-devs?

            Unassigned Unassigned
            ometa Devin Breen
            Votes:
            4 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: