Skip to content

DEVWF-T007.md

Latest commit

 

History

History
49 lines (34 loc) · 3.67 KB

DEVWF-T007.md

File metadata and controls

49 lines (34 loc) · 3.67 KB

DEVWF-T007 Set up Continuous Integration to push container images to GitHub Registry

Developers are working locally with their images to quickly develop the software. However, when they published their containers to start testing, the team notices that there is a lot of differences with their development environments.

After some research, they find that small bugs occur because the latest version was not used. Main reason is that everybody is building their own container images, and there is not a "golden image" that can be used for testing purposes. You and your team suggest to implement Continuous Integration and to push the latest version of the container image to a Container Registry hosted on GitHub after every change. This container registry can then serve as the repository that contains the latest images. These can be used and deployed on the various environments for testing and production purposes.

Challenge

In this challenge you are going to shorten the feedback loop and ensure that stable images are centrally available. For that you are going to set up a Continuous Integration Build with GitHub Actions, that builds the Docker image and pushes that to the GitHub Container Registry.

Validation

  • GitHub Container Registry populated with 3 docker images. [fabrikam-init], [fabrikam-web] and [fabrikam-api]
  • GitHub Action workflow created that builds and pushes the [fabrikam-web] image (from the content-web) to the GitHub Container Registry
  • GitHub Action workflow created that builds and pushes the [fabrikam-api] image (from the content-api) to the GitHub Container Registry
  • GitHub Action workflow created that builds and pushes the [fabrikam-init] image (from the content-init) to the GitHub Container Registry
  • Added a GitHub Secret called CR_PAT that contains the Personal Access Token to push and pull containers to the GitHub Container registry

Tips

Create a GitHub Action based on the [Publish Docker Container] startup workflow

Create a PAT token in GitHub and add it as a GitHub secret as CR_PAT to access the GitHub Container registry

Try to set some useful tags and labels in the Extract metadata step

Links & Information

Solution

If you are stuck or you want to progress to the next challenge, there is a solution prepared for you. When you run the following command from the PowerShell Terminal, a Pull Request with the files and instructions will be created for you.

Workshop-Step Solution "DEVWF-T007"

To read or view a step by step explanation of this challenge, please visit this page

Next Step

When you are done, move to the next challenge