-
Bug
-
Resolution: Fixed
-
Major
-
Jenkins 2.60.1
Blue Ocean 1.1.2 or Blue Ocean 1.1.4
-
-
Blue Ocean 1.2-beta3, Blue Ocean 1.2-beta4
If you have a custom organisation folder and try to create a pipeline with a duplicate name then the UI does not fail gracefully (the backend returns a HTTP 500 error as an IllegalArgumentException or Failure is thrown.
I tried to look through the code to see where the duplicate check was done with stock Blue Ocean but could not see any check - and the Jenkins instance will throws the same result.
Caused by: java.lang.IllegalArgumentException: team1/maven-test-project already exists at hudson.model.Items.verifyItemDoesNotAlreadyExist(Items.java:640) at hudson.model.ItemGroupMixIn.createProject(ItemGroupMixIn.java:317) at com.cloudbees.opscenter.bluesteel.folder.BlueSteelTeamFolder.createProject(BlueSteelTeamFolder.java:135) at io.jenkins.blueocean.scm.api.AbstractPipelineCreateRequest.createProject(AbstractPipelineCreateRequest.java:63) at io.jenkins.blueocean.scm.api.AbstractMultiBranchCreateRequest.createMultiBranchProject(AbstractMultiBranchCreateRequest.java:80) at io.jenkins.blueocean.scm.api.AbstractMultiBranchCreateRequest.create(AbstractMultiBranchCreateRequest.java:54) at io.jenkins.blueocean.rest.model.BluePipelineContainer.create(BluePipelineContainer.java:48) at io.jenkins.blueocean.rest.model.BluePipelineContainer.create(BluePipelineContainer.java:44) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:343)
- relates to
-
JENKINS-45482 modifying existing github org incorrect behaviour if custom blue ocean org in use
- Closed
-
JENKINS-45442 When a custom organisation is in use pipeline creation checks permissions on jenkins rather than the organistion root
- Closed
- links to