Building a Continuous Integration Workflow

Continuous integration automation tasks include cloning the repository at a specific commit, linting, building, and testing code, and evaluating changes to test coverage. The goal of continuous integration automation is to provide a guard against code changes that will lower the quality of a project or violate the rules codified in automation.

In this lesson, we will learn how to create a continuous integration workflow. In our continuous integration workflow, we will learn to execute jobs across multiple operating systems concurrently. We will install build tools onto the job executors, which we will use to build the software project. We will clone the source code for the project using an action. Finally, we will enforce passing tests and code quality by running a code linter and executing unit tests.

Introducing the tweeter command-line tool

We cannot have a continuous integration workflow without a software project to run the workflow upon. We will be using a simple Go command-line tool called tweeter. The source code for the project can be found here on GitHub.

Tweeter is a simple Go command-line tool that will send tweets to Twitter. The source code consists of two packages, main and tweeter. The tweeter package contains Go tests that will be executed by our continuous integration workflow.

Cloning and testing tweeter

Create a new repository from this template by clicking the “Use this ...