Configuration of Codedeploy Task

[Don Buchanan]

This question is in reference to Atlassian Documentation: Using the AWS CodeDeploy task

Is it possible to configure the codedeploy task? Our deployment task longer the than 900 seconds (15 seconds * 60) allocated to the task.

[Steffen Opel _Utoolity_]

This timeout does not seem to be configurable yet: Due to Atlassian's AWS CodeDeploy task being easy to confuse with the various AWS CodeDeploy tasks offered by Utoolity's Tasks for AWS add-on for Bamboo Server (notably the AWS CodeDeploy Deployment task), a user recently asked the related question How to increase the number of attempts during AWS CodeDeploy deployment? - my colleague @Henrik Opel [Utoolity] has analyzed/summarized the apparent behavior of Atlassian's CodeDeploy task as follows:

The 60 attempts limit suggests that you are using Bamboo's built in "AWS CodeDeploy" task and not the"AWS CodeDeploy Deployment" task from our (Utoolity's) Tasks for AWS add-on. Checking the source code of the former reveals that both the 15 seconds wait interval and the 60 attempts limit are fixed constants with no apparent override option.

[...]

Accordingly, you might want to watch and vote for the following newly created issue to raise Atlassian's priority regarding this notable limitation of the built-in Bamboo CodeDeploy task:

• https://jira.atlassian.com/browse/BAM-17630

Workaround via Tasks for AWS

As stated, you could work around this limitation by using Utoolity's AWS CodeDeploy Deployment task instead (part of Tasks for AWS), which also polls the status in 15 second intervals, but will indeed wait until the deployment succeeds (or explicitly fails with an error).

Please be aware though that Utoolity's task composition is a bit different from the Bamboo built in one, refer to How do the Tasks for AWS CodeDeploy tasks differ from the built-in Bamboo CodeDeploy task? for details.