Skip to content
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

adding staging bucket stack, arm builds, some directions #3205

Merged

Conversation

YashdalfTheGray
Copy link
Contributor

Summary

adds a staging bucket stack to the infrastructure, integrates arm builds

Implementation details

  • created a new build spec for the merge pipeline
  • created a staging bucket stack with a bucket policy
  • added arm builds to the pipeline so that they get signed as well
  • added a bit of instruction on how to add a new artifact to the pipeline because that's more likely what we'll need to do

Testing

  • created a stack in my personal account
  • ran through a few builds
  • things get properly signed and copied

New tests cover the changes: not applicable

Description for the changelog

Enhancement - added arm builds to the release pipeline and added a staging bucket stack

Licensing

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@YashdalfTheGray YashdalfTheGray changed the title Init agent integration adding staging bucket stack, arm builds, some directions May 6, 2022
Type: AWS::CodeBuild::Project
Properties:
Artifacts:
Type: CODEPIPELINE
ConcurrentBuildLimit: 10
Description: A sample agent build on pr
Description: A pipeline to build ECS Agent artifacts, sign them, and copy them to the staging bucket
Copy link
Contributor

@prateekchaudhry prateekchaudhry May 6, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: Is it better to say pipeline stage or just codebuild project? Also is this the project that will sign the artifacts too or is it done by SigningCodeBuildProject?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh, this is the description of the whole pipeline so I went with "pipeline" rather than "stage" and yeah, this pipeline will also sign using a CodeBuild project!

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh right! So probably it is a description of BuildAndSignCodePipeline instead?

ECS_AGENT_TAR: ecs-agent.tar
ECS_AGENT_TAR_SIGNATURE: ecs-agent.tar.asc
exported-variables:
- CODEBUILD_BUILD_ID
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Where do we use CODEBUILD_BUILD_ID? Or will we use it in later development?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yep, that's the thing that I'm going to use to take the logs from Cloudwatch logs and put the things in the S3 bucket.

Comment on lines +33 to +34
- echo "Install glibc-static for dockerfree make method"
- yum -y install glibc-static
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

not a blocker but #3206 we don't need this if we use pre-built pause containers.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@YashdalfTheGray YashdalfTheGray merged commit 7d0f5be into aws:initAgentIntegration May 9, 2022
fierlion pushed a commit to fierlion/amazon-ecs-agent that referenced this pull request May 31, 2022
* separated the merge-build and pr-build buildspecs

* aim the codebuild stack at the right buildspec

* updated the buildspecs to release and sign arm variants as well

* updated the build infrastructure to build for arm as well as amd archs

* added a note about adding more artifacts to be signed and copied

* fixing a couple of other things found in review

* added a bucket stack with a bucket policy

* missed a letter in the arm build naming

* added a missed file in the build directory structure

* updated the descriptions for all of the codebuild projects
fierlion pushed a commit to fierlion/amazon-ecs-agent that referenced this pull request May 31, 2022
* separated the merge-build and pr-build buildspecs

* aim the codebuild stack at the right buildspec

* updated the buildspecs to release and sign arm variants as well

* updated the build infrastructure to build for arm as well as amd archs

* added a note about adding more artifacts to be signed and copied

* fixing a couple of other things found in review

* added a bucket stack with a bucket policy

* missed a letter in the arm build naming

* added a missed file in the build directory structure

* updated the descriptions for all of the codebuild projects
rsheik29 pushed a commit to rsheik29/amazon-ecs-agent that referenced this pull request Jul 11, 2022
* separated the merge-build and pr-build buildspecs

* aim the codebuild stack at the right buildspec

* updated the buildspecs to release and sign arm variants as well

* updated the build infrastructure to build for arm as well as amd archs

* added a note about adding more artifacts to be signed and copied

* fixing a couple of other things found in review

* added a bucket stack with a bucket policy

* missed a letter in the arm build naming

* added a missed file in the build directory structure

* updated the descriptions for all of the codebuild projects
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants