-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Change default CodeBuild Project build container to version 4 for faster codebuild builds #11960
Comments
Hey @yvthepief , thanks for opening the issue. I'm a little hesitant about changing this default, as it would result in changes for all CDK customers that upgrade their versions (and there could potentially be differences between version 1 and version 4 that would make their builds start failing). I think we could only make this change when we release version 2.0 of the CDK, which we hope to do soon 🙂. Thanks, |
Thanks for the reply Adam (@skinny85). I understand that, hence the feature request. Lets wait on CDK 2 ;-) |
@skinny85 For the next version, instead of updating the version why not set a |
@rzamana is that possible? Is it legal to use |
how can I manually change it. |
You need to set the |
@skinny85 thank you for quick response.
|
You're putting |
@skinny85 thanks. |
You can assume a Role in your buildspec. The Role of the Project needs the correct permissions. |
Closing in favor of newer issue #16707 |
|
Short Description
Change default CodeBuild Project build container to version 4
Use Case
When creating a codebuild project, the default project buildimage is Linux Standard v1.0.
Because AWS only caches latest versions of containers, in this case version 4, a CodeBuild build with the default container version 1, the provision time takes up to 4/5 minutes instead of seconds.
Proposed Solution
Change default BuildEnvironment.LinuxBuildImage.STANDARD_1_0 to version 4 => BuildEnvironment.LinuxBuildImage.STANDARD_4_0
found in aws-cdk/packages/@aws-cdk/aws-codebuild/lib/project.ts
This is a 🚀 Feature Request
The text was updated successfully, but these errors were encountered: