-
Bug
-
Resolution: Fixed
-
Critical
-
Blue Ocean 1.1.4
-
-
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.
- relates to
-
JENKINS-45360 creating a pipeline with a duplicate name does not fail gracefully with custom Org
- Closed
-
JENKINS-45442 When a custom organisation is in use pipeline creation checks permissions on jenkins rather than the organistion root
- Closed
- links to