Difficulty: intermediate
Estimated Time: 15-30 minutes

BoxBoat Logo

Continuous Integration

Continuous Integration is an important step towards adopting containerization. This automation takes the stress off your developers, so they can continue implementing new features and fixing bugs while minimizing the time to instrument changes.

Please email feedback to: [email protected]

Continuous Integration

Step 1 of 2

Continuous Integration

For Continuous Integration, we would normally stand up a tool like Jenkins, or use something like Azure DevOps. However, we can accomplish the basic tasks right here in bash. Navigate to our source directory:

cd /root/resources/src

Step #1 - Developer pushes code

A developer working on a team pushes code to git, subversion, mercurial, etc. This is generally a manual process.

Step #2 - CI Pipeline Triggers

Your CI tool will listen on updates to your git repos. When an update is detected, it will start running. This happens automatically.

Step #3 - Build

Next, your CI pipeline will build your software. This happens automatically; however, you generally have to configure this.

To complete this task, let's write build.sh, which will build our Docker image

Step #4 - Test

Assuming the build step succeeds, the CI pipeline will test your software. This happens automatically; however, you generally have to configure this.

To complete this task, let's write test.sh, which will test our software

Step #5 - Deploy

Assuming the test step succeeds, the CI pipelines will deploy your image. This happens automatically; however, you generally have to configure this.

To complete this task, let's write deploy.sh, which will tag and push our image to a repository.