Improve 'Project with this name already exists' error with the actual project name

XMLWordPrintable

    • Type: Suggestion
    • Resolution: Fixed
    • 6.10.2
    • Component/s: Bamboo Specs
    • None
    • 1

      Problem Definition

      When we accidentally have more than one plan name clashed with a newer project Specs.java, we get this below error during runtime stating 'Project with this name already exists'.

      [INFO] Updating ownership of files in /var/atlassian/application-data/bamboo/xml-data/build-dir/serverSide/REPOSITORY_STORED_SPECS/repository-134611390/internal-yamls to bamboo
      [INFO] ------------------------------------------------------------------------
      [INFO] BUILD SUCCESS
      [INFO] ------------------------------------------------------------------------
      [INFO] Total time: 13.094 s
      [INFO] Finished at: 2019-07-01T08:55:18+01:00
      [INFO] Final Memory: 22M/378M
      [INFO] ------------------------------------------------------------------------
      Project with this name already exists.
      java.lang.IllegalStateException: Project with this name already exists.
      at com.atlassian.bamboo.configuration.external.PlanConfigImportServiceImpl.lambda$findOrCreateProjectFunction$21(PlanConfigImportServiceImpl.java:1303)
      at com.atlassian.bamboo.core.ScopedExclusionServiceImpl.withLock(ScopedExclusionServiceImpl.java:63)
      

      But it is not clear in the message which project name already exists.

      Suggested Solution

      The message should have the name of the actual project that is duplicated.

      Why this is important

      If we have multiple plans defined in Bamboo specs, it is hard to find which plan is duplicated

      Workaround (Optional) 

       There is no workaround. We will have to go through all the planSpecs.java manually to find the duplicated name.

              Assignee:
              Alexey Chystoprudov
              Reporter:
              Jeyanthan I (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: