AWS CodeBuild Concepts: Difference between revisions
Jump to navigation
Jump to search
Line 63: | Line 63: | ||
{{Internal|AWS CodeBuild Build Specification|Build Spec}} | {{Internal|AWS CodeBuild Build Specification|Build Spec}} | ||
=How the Build is Triggered= | |||
The build can be triggered manually from the console: Code Build -> Build projects -> select the project -> Start Build. | |||
The build can be triggered programmatically <font color=darkgray>How?</font>. | |||
The build can be triggered by a repository push. |
Revision as of 18:54, 13 February 2019
Internal
Build Project
Service Role
The service role, unless specified otherwise, is automatically created with the following policies:
CodeBuildBasePolicy-<build-project-name>-<region>
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Resource": [
"arn:aws:logs:us-west-2:673499572719:log-group:/aws/codebuild/playground-ops",
"arn:aws:logs:us-west-2:673499572719:log-group:/aws/codebuild/playground-ops:*"
],
"Action": [
"logs:CreateLogGroup",
"logs:CreateLogStream",
"logs:PutLogEvents"
]
},
{
"Effect": "Allow",
"Resource": [
"arn:aws:s3:::codepipeline-us-west-2-*"
],
"Action": [
"s3:PutObject",
"s3:GetObject",
"s3:GetObjectVersion",
"s3:GetBucketAcl",
"s3:GetBucketLocation"
]
}
]
}
CodeBuildVpcPolicy-<build-project-name>-<region>
CodeBuildCloudWatchLogsPolicy-<build-project-name>-<region>
For operational details on handling the service role, see
VPC
Security Group
The build project configuration allows selecting on or more security groups, which are security groups that AWS CodeBuild should use to work with the VPC. The security groups should allow outbound connections.
Environment Variables
Build Specification
How the Build is Triggered
The build can be triggered manually from the console: Code Build -> Build projects -> select the project -> Start Build.
The build can be triggered programmatically How?.
The build can be triggered by a repository push.