The following plugin provides functionality available through Pipeline-compatible steps. Read more about how to integrate steps into your Pipeline in the Steps section of the Pipeline Syntax page.
For a list of other such plugins, see the Pipeline Steps Reference page.
step([$class: 'AWSCodeDeployPublisher'])
: Deploy an application to AWS CodeDeploys3bucket
String
s3prefix
String
applicationName
String
deploymentGroupName
String
deploymentConfig
String
region
String
deploymentGroupAppspec
If checked, the build will use a dedicated appspec.yml file per deployment group.
The appspec file should be named "appspec.DEPLOYMENT_GROUP_NAME.yml" and must be present in the jenkins project workspace.
e.g.: appsec.staging.yml
boolean
waitForCompletion
If checked, this build will wait for the AWS CodeDeploy deployment to finish (with either success or failure). Polling Timeout, below, sets the maximum amount of time to wait.
If unchecked, the deployment will be handed off to AWS CodeDeploy and the build will move on to the next step.
The build will be marked a failure if either the timeout is reached or the deployment fails. The build log will indicate which.
boolean
pollingTimeoutSec
long
pollingFreqSec
long
credentials
String
versionFileName
String
deploymentMethod
String
awsAccessKey
AWS Access and Secret keys to use for this deployment. At minimum the keys must be allowed to execute codedeploy:*
and s3:Put*
. It's a best practice to have these keys be from an IAM role with limited scope.
If your Jenkins install is running on an EC2 instance with an associate IAM role, you can leave these fields blank. You will just need to ensure that the role has the correct policies.
String
awsSecretKey
AWS Access and Secret keys to use for this deployment. At minimum the keys must be allowed to execute codedeploy:*
and s3:Put*
. It's a best practice to have these keys be from an IAM role with limited scope.
If your Jenkins install is running on an EC2 instance with an associate IAM role, you can leave these fields blank. You will just need to ensure that the role has the correct policies.
String
iamRoleArn
In order to keep your application(s) more secure, this plugin only uses temporary credentials via STS, scoped to each application. To set this up:
{"Version": "2012-10-17", "Statement": [{"Effect": "Allow", "Action": ["codedeploy:*", "s3:*"], "Resource": "*"}]}
String
externalId
String
includes
String
proxyHost
Proxy host DNS name
String
proxyPort
Proxy host port
int
excludes
String
subdirectory
String
Please submit your feedback about this page through this quick form.
Alternatively, if you don't wish to complete the quick form, you can simply indicate if you found this page helpful?
See existing feedback here.