Details
-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Critical
-
Resolution: Fixed
-
Component/s: blueocean-plugin
-
Labels:
-
Environment:Blue Ocean 1.1.4
-
Similar Issues:
-
Epic Link:
-
Sprint: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
-
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
Activity
Field | Original Value | New Value |
---|---|---|
Assignee | James Nord [ teilo ] |
Status | Open [ 1 ] | In Progress [ 3 ] |
Link |
This issue relates to |
Link |
This issue relates to |
Sprint | Blue Ocean 1.2-beta3 [ 346 ] |
Rank | Ranked higher |
Epic Link | JENKINS-35759 [ 171771 ] |
Rank | Ranked higher |
Sprint | Blue Ocean 1.2-beta3 [ 346 ] | Blue Ocean 1.2-beta3, Blue Ocean 1.2-beta4 [ 346, 361 ] |
Resolution | Fixed [ 1 ] | |
Status | In Progress [ 3 ] | Resolved [ 5 ] |
Remote Link | This issue links to "CloudBees Internal CJP-7286 (Web Link)" [ 19005 ] |
Status | Resolved [ 5 ] | Closed [ 6 ] |
Assignee | James Nord [ teilo ] |