Github Actions by Example
  • GitHub Actions by Example
  • chap1-intro
    • Section 1 - Introducing GitHub Actions
    • Section 2 - Terminology and Core Concepts
    • Section 3 - Building a workflow
  • chap2-deployment-workflow
    • Section 1 - Workflow
    • Section 2 - The services
    • Section 3 - The test workflow job
    • Section 4 - The build and push workflow job
    • Section 5 - The deploy workflow job
  • Chap3-reusable-workflows
    • Section 1 - What is a reusable workflow
    • Section 2 - The test reusable workflow
    • Section 3 - The build and push reusable workflow
    • Section 4 - The deploy reusable workflow
    • Section 5 - Releasing the reusable workflow
  • Chap4-custom-actions
    • Section 1 - What is a custom action
    • Section 2 - Composite Custom Actions
    • Section 3 - Javascript Custom Actions
Powered by GitBook
On this page
  • Services we will deploy
  • The test workflow job
  • The build-and-push workflow job
  • The deploy workflow job
  1. chap2-deployment-workflow

Section 1 - Workflow

In this chapter, we will delve deeply into GitHub Action workflows by examining a multi-job deployment workflow. This workflow encompasses several key processes: running tests to validate the service, building a Docker image, uploading this image to the GitHub registry, and ultimately initiating the deployment process.

Services we will deploy

We will deploy two straightforward Golang HTTP services: the workout-management-service and the user-management-service. The implementation details of these services are not critical from a workflow standpoint, so feel free to skip Section 2 ('s2-the-services') if you are not interested in the implementation specifics.

The test workflow job

This job within the workflow is tasked with executing the unit tests to verify that the service is functioning as expected.

The build-and-push workflow job

This job focuses on constructing the Docker image and pushing it to the GitHub registry.

The deploy workflow job

The responsibility of this job is to trigger the deployment of the service.

Previouschap2-deployment-workflowNextSection 2 - The services

Last updated 8 months ago