GitHub Actions uses workflows so that you can include DevOps processes in any GitHub repository. GitHub Actions lets the build repository interact with various services in a deployment process. Commonly, a codebase will be built and pushed into a container registry for deployment later. In this post, I show you how to build and push the Octopus Deploy underwater app to Amazon Elastic Container Registry (ECR) using GitHub Actions. Getting started To follow along, you need: An Amazon Web Services (AWS) account A GitHub account This post uses the . You can fork the repository and follow along. Alternatively, the github-ecr branch contains the template files you need to complete the steps in this post. You have to replace some values with your own, but I include my values in this post as a reference. Octopus underwater app repository Amazon Web Services setup To set up AWS for GitHub Actions, you need to create an access key and an ECR repository to store the image. To create an access key, go to , then , then , , then , and then . Amazon Console IAM Users [your user] Security credentials Create Access Key Your browser downloads a file containing the Access Key ID and the Secret Access Key. These values are used in GitHub to authenticate to Amazon. To create a repository, go to the , then , and then . Amazon Console ECR Create Repository You need to set up an image repository for each image that you publish. Give the repository the same name you want the image to have. You will see your repository under , then . Make a note of the zone it's in, in the URI field. Amazon ECR Repositories GitHub setup In this post, you build the Octopus Deploy underwater app repository and push it to Amazon ECR. You use these images in later blog posts. Fork the repository at . https://github.com/terence-octo/octopus-underwater-app-docker Go to , then , and then . Settings Secrets New repository secret - the name of the AWS ECR repository you created REPO_NAME - the Access Key ID from earlier AWS_ACCESS_KEY_ID - the Secret Access Key from earlier AWS_SECRET_ACCESS_KEY You need to create a workflow file in the repository. A GitHub Actions workflow contains instructions on performing operations on the code repository. These are community-maintained steps. Several pre-built step templates allow you to do many different tasks on a code repository. In this example, you use a step template to build and push the code to an AWS ECR repository. Create a file named in the .github/workflows directory of the root folder. Paste the following code in the main.yml file: main.yml on:
  push:
    branches: [ main ]
  pull_request:
    branches: [ main ]

name: AWS ECR push

jobs:
  deploy:
    name: Deploy
    runs-on: ubuntu-latest

    steps:
    - name: Checkout
      uses: actions/checkout@v2

    - name: Configure AWS credentials
      uses: aws-actions/configure-aws-credentials@v1
      with:
        aws-access-key-id: ${{ secrets.AWS_ACCESS_KEY_ID }}
        aws-secret-access-key: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
        aws-region: us-east-2

    - name: Login to Amazon ECR
      id: login-ecr
      uses: aws-actions/amazon-ecr-login@v1

    - name: Build, tag, and push the image to Amazon ECR
      id: build-image
      env:
        ECR_REGISTRY: ${{ steps.login-ecr.outputs.registry }}
        ECR_REPOSITORY: ${{ secrets.REPO_NAME }}
        IMAGE_TAG: latest
      run: |
        # Build a docker container and push it to ECR 
        docker build -t $ECR_REGISTRY/$ECR_REPOSITORY:$IMAGE_TAG .
        echo "Pushing image to ECR..."
        docker push $ECR_REGISTRY/$ECR_REPOSITORY:$IMAGE_TAG
        echo "::set-output name=image::$ECR_REGISTRY/$ECR_REPOSITORY:$IMAGE_TAG" GitHub starts an action by using a push or pull request on the main branch. The steps check out the code, authenticate and log into AWS, then build, tag, and push the image to Amazon ECR. A similar step template could push to other cloud repositories like Google or Microsoft. Commit your changes, go to the tab, and click the title of your commit message. You see the various stages of the workflow as it reaches completion. Actions Go to your Amazon ECR repository to view the image. Conclusion In this post, you set up a GitHub Actions workflow to build and push an image to Amazon ECR. Deployment tools can then use this image in a later deployment stage to deploy the web application to a service. GitHub Actions allows code repositories to be part of a deployment process without additional work. GitHub Actions has several templates that developers can use to perform other deployment tasks. Happy deployments! Also published here.

Everything as Code (EaC): What Is It and Why Is It Important? 

How to Get Started With Bamboo

Too Long; Didn't Read

Make resilience your competitive advantage

Effortlessly Deploy a Docker Image to ECR with GitHub Actions

About Author

Comments

TOPICS

THIS ARTICLE WAS FEATURED IN

Related Stories

Untitled Story

Containerization and Its Benefits

104 Stories To Learn About Continuous Integration

139 Stories To Learn About Cicd

15 of the Best Continuous Delivery Tools

Improving the Working Environment for Developers - In 3 Stages Only

Containerization and Its Benefits

104 Stories To Learn About Continuous Integration

139 Stories To Learn About Cicd

15 of the Best Continuous Delivery Tools

Improving the Working Environment for Developers - In 3 Stages Only

Light-Mode

Classic

Newspaper

Dark-Mode

Neon Noir

Minty

HN StartUps