CloudBees action: Deploy to Amazon ECS

Use this action to deploy to an Amazon Elastic Container Service (ECS), using either the service name or an ECS task definition.

All CloudBees action repositories are listed at CloudBees, Inc. on GitHub.

Inputs

Table 1. Input details
Input name	Data type	Required?	Description
`task-definition`	String	No	The path to the ECS task definition JSON file. Required only if `service` not specified.
`service`	String	No	The name of the ECS service to deploy to. Required only if `task-definition` not specified.
`cluster`	String	Yes	The name of the ECS cluster to deploy to.
`wait-for-service-stability`	Boolean	Yes	Whether to wait for the ECS service to reach a stable state after deploying the new task definition. Default value is `false`. When `false`, there is no waiting.
`wait-for-minutes`	String	Yes	The amount of time to wait for the ECS service to reach a stable state, in minutes. The default is `30 minutes`, and the maximum time allowed is `6 hours`.
`force-new-deployment`	Boolean	Yes	Whether to force a new service deployment. Default value is `false`. When `false`, the new deployment is not forced.

Usage example

In your YAML file, add:

      - name: Deploy task definition
        uses: cloudbees-io/ecs-deploy-task-definition@v1
        with:
          task-definition: test/taskDefinition.json
          service: ECS_service_name
          cluster: ECS_cluster_name
          wait-for-service-stability: true
          wait-for-minutes: 6 hours
          force-new-deployment: true▼