Incorrect Link in the system error page for deployment failure

XMLWordPrintable

    • Type: Bug
    • Resolution: Won't Fix
    • Priority: Low
    • n/a
    • Affects Version/s: 10.2.9, 12.1.2
    • Component/s: Deployments
    • None
    • 1
    • Severity 3 - Minor
    • 1

      Issue Summary

      When a system error occurs during a deployment in Bamboo, the error entry shown on /admin/systemErrors.action generates an invalid link pointing to /browse/{deploymentProjectId}-{environmentId} (e.g. /browse/1234567-8901234). This URL format is only valid for build plan keys (e.g. /browse/PROJ-PLAN), not for deployment entities.

      The same error, when viewed from the Deployment Result page (/deploy/viewDeploymentResult.action), is displayed correctly because that page passes the deploymentResult context to the rendering macro, which suppresses the broken link.

      Steps to Reproduce

      1. Set up a Deployment Project with at least one Environment in Bamboo.
      1. Trigger a deployment that will fail (e.g. configure a deployment task that references a non-existent agent capability, or a script task that exits with an error that gets logged as a system error, or an SSH task with an unknown hosts, etc).
      1. Navigate to Bamboo Administration → System → System Errors (/admin/systemErrors.action).
      1. Observe the error entry for the failed deployment — it will display a link like:
        <https://<bamboo-url>>/browse/1234567-8901234
        where 1234567 is the Deployment Project ID and 8901234 is the Environment ID.
      1. Click the link.

      Expected Results

      The error link should point to the Deployment Result page:

      • /deploy/viewDeploymentResult.action?deploymentResultId={deploymentResultId}

      and the error entry should display the deployment environment name rather than the raw numeric key.

      Actual Results

      The link points to /browse/{deploymentProjectId}{environmentId} which returns an Internal Server Error. If a resultNumber is also present, a second link is rendered as /browse/{deploymentProjectId}{environmentId}-{deploymentResultId}, which is equally invalid.

      An Internal Server Error is thrown:

      nternal server error
      Go to...
      Site homepage
      A system error has occurred - our apologies!
      Please create a problem report on our support system at https://support.atlassian.com with the following information:
      
      a description of your problem and what you were doing at the time it occurred
      cut & paste the error and system information found below
      attach the atlassian-bamboo.log log file found in your application home.
      We will respond as promptly as possible.
      Thank you!
      Version: 12.1.2
      Build: 120105
      Build Date: Thu Feb 05 09:45:06 UTC 2026
      
      Request information:
      Request URL: https://linux-120563.prod.atl-cd.net/bamboo/build/viewBuildSummary.action
      Scheme: https
      Server: linux-120563.prod.atl-cd.net
      Port: 443
      URI: /bamboo/build/viewBuildSummary.action
      Context path: /bamboo
      Servlet path: /build/viewBuildSummary.action
      Path info:
      Query string: buildKey=1081345-1245185
      Stack Trace:
      
      java.lang.IllegalArgumentException: Could not parse key '1081345-'
      	at com.atlassian.bamboo.plan.PlanKeys.getPlanKey(PlanKeys.java:269)
      	at com.atlassian.bamboo.plan.PlanKeys.getPlanKey(PlanKeys.java:112)
      

      Workaround

      Click on View error log in the system error instead of Deployment ID

              Assignee:
              Unassigned
              Reporter:
              Venkata Sateesh Pentela
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: