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

Edit Pipeline in Blue ocean resets scm behaviors for all pipeline in Github Org

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Critical Critical
    • blueocean-plugin
    • None
    • Blue Ocean 1.2
      Jenkins 2.60.3

      When I edit a pipeline in Blue Ocean editor it resets the scm checkout behaviors for all my Pipelines. I'm using Github scm.

      Steps:
      1. Create a pipeline in blue ocean editor for a github project
      2. Switch to classic UI
      3. Configure the Github Organization Pipeline scm - Add "Clean Build Behavior"
      4. Run the Pipeline - notice clean build behavior working
      5. Edit Pipeline in the Blue Ocean editor and save any change
      2. Switch to classic UI
      3. Configure the Github Organization Pipeline scm

      Expected:
      Clean Build behavior to still be present

      Actual:
      Clean Build has been removed

      This is doubly bad because editing any Pipeline in one github organization will side effect to all Pipelines in that organization. Further, it happen silently so users will have difficulty figuring out what happened and why.

          [JENKINS-46438] Edit Pipeline in Blue ocean resets scm behaviors for all pipeline in Github Org

          Michael Neale added a comment - - edited

          Thanks bitwiseman - kind of actually knew this would be a problem (there were always dark corners)

          This, but mostly the fact that you cant set prefs per pipeline has pushed blue ocean away from org folders. 

          As of yesterday org folders was removed from master of blue ocean: https://github.com/jenkinsci/blueocean-plugin/pull/1336 - so this class of problem goes away (not so much that it was fixed, but goes away) - would be good if you tried that out. it now creates things as regular MBP - no more org folder (product based decision). 

          So I think I will mark this as a duplicate, in a way, if that is ok? This could also be cherry picked to a 1.2.1 release if warranted. 

          Michael Neale added a comment - - edited Thanks bitwiseman - kind of actually knew this would be a problem (there were always dark corners) This, but mostly the fact that you cant set prefs per pipeline has pushed blue ocean away from org folders.  As of yesterday org folders was removed from master of blue ocean: https://github.com/jenkinsci/blueocean-plugin/pull/1336  - so this class of problem goes away (not so much that it was fixed, but goes away) - would be good if you tried that out. it now creates things as regular MBP - no more org folder (product based decision).  So I think I will mark this as a duplicate, in a way, if that is ok? This could also be cherry picked to a 1.2.1 release if warranted. 

          Michael Neale added a comment -

          vivek this should be gone now as of master right? 

           

          Or does save pipeline now also save config in a way that this could be a similar problem? 

          Michael Neale added a comment - vivek this should be gone now as of master right?    Or does save pipeline now also save config in a way that this could be a similar problem? 

          Michael Neale added a comment -

          checked with newer version - seems to not have this behavior which is good. 

          Michael Neale added a comment - checked with newer version - seems to not have this behavior which is good. 

          Liam Newman added a comment -

          Yes, cherry pick this into 1.2.1, please.

          Liam Newman added a comment - Yes, cherry pick this into 1.2.1, please.

            Unassigned Unassigned
            bitwiseman Liam Newman
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: