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

modifying existing github org incorrect behaviour if custom blue ocean org in use

XMLWordPrintable

    • Blue Ocean 1.2-beta3, Blue Ocean 1.2-beta4

      If a custom blue ocean organisation is in use and it uses a root item that is not Jenkins then modifying existing GitHub organistaions fails.

      THis is most likely due to the fact that the code to check to see if this is a new pipeline always returns true as the custom org folder is completely ignored.

          [JENKINS-45482] modifying existing github org incorrect behaviour if custom blue ocean org in use

          James Nord created issue -
          James Nord made changes -
          Assignee New: James Nord [ teilo ]
          James Nord made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]
          James Nord made changes -
          Link New: This issue relates to JENKINS-45360 [ JENKINS-45360 ]
          James Nord made changes -
          Link New: This issue relates to JENKINS-45442 [ JENKINS-45442 ]
          James Dumay made changes -
          Sprint New: Blue Ocean 1.2-beta3 [ 346 ]
          James Dumay made changes -
          Rank New: Ranked higher
          James Dumay made changes -
          Epic Link New: JENKINS-35759 [ 171771 ]
          James Dumay made changes -
          Rank New: Ranked higher
          James Dumay made changes -
          Sprint Original: Blue Ocean 1.2-beta3 [ 346 ] New: Blue Ocean 1.2-beta3, Blue Ocean 1.2-beta4 [ 346, 361 ]
          James Nord made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: In Progress [ 3 ] New: Resolved [ 5 ]

            Unassigned Unassigned
            teilo James Nord
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: