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

This issue is archived. You can view it, but you can't modify it. Learn more

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.

            Assignee:
            Unassigned
            Reporter:
            James Nord
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: