input_bucket

output_bucket

Become an AWS pro with CodePipeline suite. Developed by AWS Solution Certified Architects, get hands-on with CI/CD tools—no setup, no cleanup, no hassle. Deploy Java and Node.js apps easily.

CD Using Native Tools Available on AWS-01.png

Dockerfile.tar.gz

aws_access_key_id

aws_region

aws_secret_access_key

spa_terminal

spa_terminal-copy

spa_terminal-copy-copy

The CodePipeline suite is a solution developed by Amazon Web Services (AWS) for continuous integration and continuous delivery (CI/CD). It can be used to create automated pipelines on the AWS environment and allows the deployment of code modifications on the go. This course explains the fundamentals of the DevOps culture and why organizations adopt it. 

In this course, you will learn how the different components of AWS CodePipeline work together, from managing repositories to building automation and handling CI and CD alike. You will first get introduced to continuous integration and continuous delivery/deployment, followed by various CI/CD tools. Next, you will learn the basics of CodeCommit, CodeBuild, CodeDeploy, and CodePipeline. Finally, you will use CodePipeline to deploy a Java application. 

This course will help you form a strong foundation in DevOps tools. By the end of this course, you’ll gain hands-on experience deploying a Node.js and Java application using the CodePipeline suite.

CI/CD Using Native Tools Available on AWS

# Working with branches

A **branch** is simply a folder or a separate place where a developer/collaborator can organize their work without affecting other works in the main repository. There is usually a default branch that serves as a central place where the latest changes are stored. This default branch is usually named the main branch, master branch, but can be any other name chosen by a development team.

## Adding files to a repository
To quickly get started with CodeCommit, new files can be created right from the AWS CLI or uploaded using Git from a local computer.

> **Note**: When a new repository is created, it is empty, and initial configurations need to be done. The fastest way to get the repository ready is by creating a new file from the console. The other option includes cloning the repository using an HTTPS/SSH connection, making changes, and then pushing the changes back to the repository.

Files can be added to a branch using the ```put-file``` command as shown below:

```
aws codecommit put-file --repository-name CICD_on_AWS --branch-name main --file-content file:///usercode/helloWorld.txt --file-path /helloWorld.txt --name "John Doe" --email "john.doe@example.com"
```
> **Note**: A text file `helloWorld.txt` has been created in the path `/usercode/` for your practice.

The required parameters include the following:

- `repository-name`: This is the name of the repository.
- `branch-name`: This is the name of the branch to add the file(s) to.
- `file-content`: This is the file to add.
- `file-path`: This is the path to place the file in the repository.
- `parent-commit-id`: This is a unique commit ID for the commit.
- `name`: This is the name to attach to the commit.
- `email`: This is the email to attach to the commit.
- `commit-message`: This is the commit message to attach to the commit.

## View information about a specific branch

We can use the `get-branch` command to get information about a branch.



Learn how to work with branches in CodeCommit.

Introduction to the Course

What is CI/CD?

Basics of CodeCommit

Basics of CodeBuild

Basics of CodeDeploy

Code Pipeline with a Sample Node.js Application

Building CI/CD Pipeline with AWS CodePipeline

COURSE ASSESSMENT

CodePipeline with a Sample Java Application

Bringing the Learnings Together

Working with Branches in CodeCommit