The CodeBuild project is generated from the DSL and created with CloudFormation. By default, the files that the DSL evaluates are:


To create the CodeBuild project, you run:

cody deploy

You’ll see output that looks something like this:

$ cody deploy
Generated CloudFormation template at /tmp/codebuild.yml
Deploying stack demo-cody with CodeBuild project demo
Creating stack demo-cody. Check CloudFormation console for status.
Stack name demo-cody status CREATE_IN_PROGRESS
Here's the CloudFormation url to check for more details
Waiting for stack to complete
03:04:30AM CREATE_IN_PROGRESS AWS::CloudFormation::Stack demo-cody User Initiated
03:04:35AM CREATE_IN_PROGRESS AWS::IAM::Role IamRole Resource creation Initiated
03:04:56AM CREATE_IN_PROGRESS AWS::CodeBuild::Project CodeBuild
03:04:58AM CREATE_IN_PROGRESS AWS::CodeBuild::Project CodeBuild Resource creation Initiated
03:04:59AM CREATE_COMPLETE AWS::CodeBuild::Project CodeBuild
03:05:01AM CREATE_COMPLETE AWS::CloudFormation::Stack demo-cody
Stack success status: CREATE_COMPLETE
Time took for stack deployment: 30s.

Explicit CodeBuild Project Name

By default, the CodeBuild project name is inferred and is the parent folder that you are within. You can explicitly specify the project name as the first CLI argument:

cody deploy my-project


By default, cody looks up files in the .cody folder. Example:


You can use the --type option to tell the tool to lookup files in a subfolder. Here’s an example.

cody deploy PROJECT_NAME --type deploy

This will look up buildspec.yml, project.rb, and role.rb files in the .cody/deploy folder. So:


Likewise cody deploy PROJECT_NAME --type unit would result in:


Also, for help info you can check the cody deploy CLI reference.

Pro tip: Use the <- and -> arrow keys to move back and forward.

Edit this page

See a typo or an error? You can improve this page. This website is available on GitHub, and contributions are encouraged and welcomed. We love pull requests from you!