Endless waiting / queued deployment jobs

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Low
    • 6.3.0
    • Affects Version/s: 5.11.3
    • Component/s: None
    • None
    • Severity 3 - Minor

      Summary

      Deployment plan infinitely queued / waiting and not being picked up despite available agents.

      Steps to Reproduce

      1. Generate a build plan with 2 tasks, the last task is to produce a shared artifact.
      2. Define a deployment project and use the shared artifact.
      3. Run the build, create a release and deploy it.
      4. Remove the second task from build plan, this removes the shared artifact definition.
      5. Run the build (which does not create a shared artifact anymore).
      6. Create a release and click on "Start deployment"

      Expected Results

      Fail the build gracefully with meaningful communication.

      Actual Results

      Deployment Plan is queued infinitely.

      The below exception is thrown in the atlassian-bamboo.log / catalina.out file:

      2016-07-15 10:39:31,602 WARN [10-BAM::PlanExec:pool-18-thread-1] [ArtifactDownloaderRuntimeDataProvider] Unable to find an artifact definition for name: ...
      2016-07-15 10:39:31,602 ERROR [10-BAM::PlanExec:pool-18-thread-1] [ChainPluginSupportHelper] Task context data provider failed:java.lang.IllegalArgumentException: Unable to find an artifact definition for name: ...
      2016-07-15 10:39:31,602 INFO [10-BAM::PlanExec:pool-18-thread-1] [DefaultErrorHandler] Recording an error: com.atlassian.bamboo.plugins.bamboo-artifact-downloader-plugin:artifactdownloadertask : 222068744-222134304 : Unable to find an artifact definition for name: ...
      
      

      Notes

      Environment deployment history page (https://mydomainhere/bamboo/deploy/viewEnvironment.action?id=9273345) shows the deployment e.g. as "Waiting for xxx minutes".

      Workaround

      When you re-add the artifact definition to the build task, run the build, re-select the artifact in deployment project tasks, create a release and click on start deployment, the deployment will be executed. All older deployment jobs stay in queue forever as "queued".

            Assignee:
            Marcin Gardias
            Reporter:
            ChristianW
            Votes:
            6 Vote for this issue
            Watchers:
            10 Start watching this issue

              Created:
              Updated:
              Resolved: