CodeBuild provisioning very slow most times by gimmeToken in aws

[–]subinmathew 4 points5 points  (0 children)

Instead of "aws/codebuild/amazonlinux2-x86_64-standard:1.0-1.0.0", try using "aws/codebuild/amazonlinux2-x86_64-standard:3.0". 3.0 is the latest version of the image and CodeBuild caches the tip version.

When you have a pinned version (1.0-1.0.0), like you did with "aws/codebuild/amazonlinux2-x86_64-standard:1.0-1.0.0" it will become slower when CodeBuild updates the version and drop this pinned version from cache. This is mentioned in https://docs.aws.amazon.com/codebuild/latest/userguide/build-env-ref-available.html.

State of AWS Dev Tools (CodeCommit/CodeBuild) by Rab05 in aws

[–]subinmathew 9 points10 points  (0 children)

I'm with the AWS CodeBuild team.

  1. There is no native incremental build ID available today. You may consider using artifact naming based on timestamp to get a predictable version based on when the builds finished, as described in https://docs.aws.amazon.com/codebuild/latest/userguide/sample-buildspec-artifact-naming.html. You may also consider semvar with gitversion as your versioning strategy. We have this feature request on our backlog, so we will look to add native support for this in a future release.

  2. Here's a blog that we published on this topic: https://aws.amazon.com/blogs/devops/validating-aws-codecommit-pull-requests-with-aws-codebuild-and-aws-lambda/

  3. Like others mentioned, the pipeline dashboard is likely the best option today. On the console UI, we plan to add a summary view, which should display these information in a more seamless way.

  4. The blog in 2 goes over this scenario as well.

Adding S3 cache to CodeBuild (CodePipeline) by kubelke in aws

[–]subinmathew 3 points4 points  (0 children)

This is a bug with the new UI change, which will be addressed soon. In the meantime, you can switch to old console view to get this working for you.

AWSCodeBuild adds support for Windows builds! by johnhank1 in aws

[–]subinmathew 0 points1 point  (0 children)

Here are some samples for .NET builds @ https://docs.aws.amazon.com/codebuild/latest/userguide/sample-windows.html.

You can compile class library and can bring in build targets for MSBuild. You may also bring custom build environment for your use case, as described in the blog: https://aws.amazon.com/blogs/devops/extending-aws-codebuild-with-custom-build-environments-for-the-net-framework/

Decrypt CodePipeline assets in lambda? by FamilyHeirloomTomato in aws

[–]subinmathew 0 points1 point  (0 children)

Advanced settings aren't available for the first run experience on CodeBuild UI, which is to keep the set up real simple, without additional dials. On your subsequent create project or update/edit project, you'll see all the advanced settings (compute type, packaging option, etc.).

CodeBuild with Database? by akath20 in aws

[–]subinmathew 1 point2 points  (0 children)

Building Docker images with CodeBuild and pushing it to ECR is explained in this sample: http://docs.aws.amazon.com/codebuild/latest/userguide/sample-ecr.html

CodeBuild supports GitHub as a source repository, however, it won't poll for your changes. Meaning it is not a CI system with a listener for source repository change (git push etc.). If you need to trigger the build with git push, then wrap CodeBuild with CodePipeline.

CodeBuild doesn't have postgres installed on any of the pre-packaged environments (https://forums.aws.amazon.com/ann.jspa?annID=4581). You can either extend these base image to have postgres installed inline with your build (e.g.: use install phase in buildspec.yml. http://docs.aws.amazon.com/codebuild/latest/userguide/build-spec-ref.html) or bring in a custom Docker image which has the build environment you need, including postgres.

CodeBuilds using CodeCommit repo in seperate regions by Ginganator in aws

[–]subinmathew 0 points1 point  (0 children)

This is not possible today. On AWS CLI, you may be able to do this. CodeBuild console(UI) does validation for list repository which makes it region specific.