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

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

    XMLWordPrintable

Details

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

    Description

      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.

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-45360 creating a pipeline with a duplicate name does not fail gracefully with custom Org

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-45442 When a custom organisation is in use pipeline creation checks permissions on jenkins rather than the organistion root

          • Major - Major loss of function.
          • Closed
          links to

          Web Link CloudBees Internal CJP-7286

          Activity

            There are no comments yet on this issue.

            People

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

              Dates

                Created:
                Updated:
                Resolved: