Skip to content

Latest commit

 

History

History
109 lines (74 loc) · 4.03 KB

README.md

File metadata and controls

109 lines (74 loc) · 4.03 KB

Lab 1 - CodeCommit

This lab will provide an introduction into using CodeCommit for version control. In this lab we will cover:

  • Creating and using a repository
  • Start and manage a new branch
  • Push files to CodeCommit as commits
  • Open and merge a pull request [On hold for now..]

Creating a CodeCommit repository

To create a new CodeCommit repository using the AWS CLI, run the following command from a terminal window on your cloud9 insatance:

aws codecommit create-repository --repository-name CICD --repository-description "My repository for the CI/CD Workshop"

After running this command, a json object containing Metadata is returned. Here is an example of this object:

{
    "repositoryMetadata": {
        "accountId": "111111111111",
        "repositoryId": "6d17a8c7-d64f-43c7-b5ba-0c3ecea54a95",
        "repositoryName": "CICD",
        "repositoryDescription": "My repository for the CI/CD Workshop",
        "lastModifiedDate": 1603917692.782,
        "creationDate": 1603917692.782,
        "cloneUrlHttp": "https://git-codecommit.eu-west-1.amazonaws.com/v1/repos/CICD",
        "cloneUrlSsh": "ssh://git-codecommit.eu-west-1.amazonaws.com/v1/repos/CICD",
        "Arn": "arn:aws:codecommit:eu-west-1:111111111111:CICD"
    }
}

For this lab, we will need the value of the cloneUrlHttp for cloning the repo. More details on the metadata and the Create Repository command can be here

Cloning the application source repository.

We are going to clone the repository created in the previous section using the git clone command:

git clone https://github.com/pedreviljoen/aws-ci_cd_workshop_source.git <name-of-folder>

replacing [cloneUrlHttp] with the value returned when the repostory was created.

Note: After cloning the repository, we would have cloned the NodeJS application source repository. We will use this to build onto the next labs.

Change the remote URL to CodeCommit repository

At this step we need to change the remote of our repository to point to our created CodeCommit repository. First we check our existing remote, which should have the below output:

git remote -v
> origin  https://github.com/pedreviljoen/aws-ci_cd_workshop_source (fetch)
> origin  https://github.com/pedreviljoen/aws-ci_cd_workshop_source (push)

Now we change the remote to point to our CodeCommit repository.

git remote set-url origin https://git-codecommit.eu-west-1.amazonaws.com/v1/repos/CICD

To confirm we can run the below command to check if we have updated the remote of the repository:

git remote -v
> origin https://git-codecommit.eu-west-1.amazonaws.com/v1/repos/CICD (fetch)
> origin https://git-codecommit.eu-west-1.amazonaws.com/v1/repos/CICD (push)

Configuring your git user name and email on the cloud 9 instance.

While this is not necessary, use the following commands to set your git username and email address. These willbe the details used for commits:

git config --global user.name "My Username"
git config --global user.email [email protected]

We are going to clone a sample application from another repository to use for our CodeCommit repository.

  1. Next we add, commit and push the files of the NodeJS project to our CodeCommit repository
git add .
git commit -m 'Init NodeJS application repository'
git push origin main

Here are links that proide more detials on the git add, git commit and git push commands.

Creating a new branch

To create a new branch for development, use the git checkout command:

git checkout -b dev
git push origin dev

View the Repository using the AWS Console

To view this newly created repo in the AWS console, use this link