Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

awsCodeBuild projectName: 'project', credentialsType: 'keys', region: 'us-west-2', sourceControlType: 'jenkins'

 


View without Jenkins Blue Ocean plugin:

...

(Recommended) View with Jenkins Blue Ocean plugin:

 


Using AWS CodeBuild with Jenkins

...

AWS Credentials in Jenkins

When using credentialsType: 'keys' or creating new CodeBuild Credentials in JenkinsIt's recommended to use the Jenkins credentials store for your AWS credentials. Your Jenkins credentials must be of type CodeBuild Credentials to be compatible with the CodeBuild plugin. When creating new CodeBuild Credentials, the plugin will attempt to use the default credentials provider chain if if AWS access and secret keys are not defined.

You can also specify your AWS access and secret keys in the CodeBuild configuration when using credentialsType: 'keys'. If the access and secret keys are not specified, the plugin will attempt to use the default credentials provider chain. When running a Jenkins pipeline build, the plugin will attempt to use credentials from the pipeline-aws plugin before falling back to the default credentials provider chain. If you are running Jenkins on an EC2 instance, leave the AWS Access Key and AWS Secret Key fields blank to use the access and secret key fields blank and specify credentialsType: 'keys' to use credentials from your EC2 instance profile, which is in the default credentials provider chain.