Build CI/CD Pipeline in 5 Steps with GitHub Actions

Introduction

Did you know that 87% of developers say that optimizing their CI/CD pipeline is a top priority, but only 23% have successfully implemented a fully automated workflow? In this era of rapid development and deployment, having a streamlined pipeline is crucial for efficiency and productivity. In this article, you will build a CI/CD pipeline in 5 steps using GitHub Actions, a free tool that simplifies the process. By the end of this tutorial, you will have a fully functional pipeline that automates your testing, building, and deployment process, making you more efficient in 2026. To get started, make sure you have the following prerequisites:

• A GitHub account
• A basic understanding of YAML
• A Python project to automate (you can use any Python project, even a simple "Hello World" script)
• Docker installed on your machine

Table of Contents

• Introduction
• Step 1 — Create a GitHub Actions Workflow
• Step 2 — Define the Build Process
• Step 3 — Automate Testing
• Step 4 — Deploy to Production
• Step 5 — Monitor and Log
• Real-World Usage
• Real-World Application
• Conclusion
• 💬 Your Turn

Step 1 — Create a GitHub Actions Workflow

Creating a GitHub Actions workflow is the first step in building your CI/CD pipeline. This step matters because it sets up the foundation for your automated process. Create a new file in your repository's .github/workflows directory, e.g., .github/workflows/main.yml, and add the following code:

name: Main Workflow

on:
  push:
    branches:
      - main

jobs:
  build-and-deploy:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout code
        uses: actions/checkout@v2

Expected output: Your workflow file should be created and committed to your repository.

Step 2 — Define the Build Process

Defining the build process is crucial for automating your pipeline. This step matters because it ensures that your code is built correctly before deployment. Add the following code to your main.yml file:

      - name: Set up Python
        uses: actions/setup-python@v2
        with:
          python-version: '3.x'

      - name: Install dependencies
        run: |
          python -m pip install --upgrade pip
          pip install -r requirements.txt

Expected output: Your dependencies should be installed, and your Python environment should be set up.

Step 3 — Automate Testing

Automating testing is essential for ensuring the quality of your code. This step matters because it saves you time and reduces the risk of human error. Add the following code to your main.yml file:

      - name: Run tests
        run: |
          python -m unittest discover -s tests

Expected output: Your tests should run, and you should see the results in your workflow log.

Step 4 — Deploy to Production

Deploying to production is the final step in your pipeline. This step matters because it gets your code to your users. Add the following code to your main.yml file:

      - name: Deploy to production
        uses: appleboy/scp-action@master
        with:
          host: ${{ secrets.HOST }}
          username: ${{ secrets.USERNAME }}
          password: ${{ secrets.PASSWORD }}
          source: "."
          target: "/var/www/html"

Expected output: Your code should be deployed to your production server.

Step 5 — Monitor and Log

Monitoring and logging are crucial for identifying issues and improving your pipeline. This step matters because it helps you debug and optimize your process. Add the following code to your main.yml file:

      - name: Log deployment
        run: |
          echo "Deployment successful!"

Expected output: You should see a log message indicating that your deployment was successful.

Real-World Usage

Now that you have built your CI/CD pipeline, you can use it to automate your development workflow. For example, you can use it to deploy a Python web application to a cloud server. You can also use tools like Vultr Cloud to host your application and DigitalOcean to deploy your code.

Real-World Application

This pipeline can be used to solve real-world problems, such as automating the deployment of a web application. By using GitHub Actions, you can simplify your workflow and reduce the risk of human error. You can also use this pipeline as a starting point for more complex workflows, such as automating testing and deployment for a microservices architecture.

Conclusion

In this article, you built a CI/CD pipeline in 5 steps using GitHub Actions. Here are three specific takeaways:

1. GitHub Actions is a powerful tool for automating your development workflow.
2. You can use GitHub Actions to automate testing, building, and deployment.
3. By using a CI/CD pipeline, you can simplify your workflow and reduce the risk of human error. What to build next? Try adding more complexity to your pipeline by automating testing for multiple environments.

💬 Your Turn

Have you automated your CI/CD pipeline before? What was your approach? Drop it in the comments — I read every one.

💡 Found this helpful?

If this tutorial saved you time or solved a problem, consider:

• 
• 

Every coffee or donation keeps me writing free tutorials like this one!

---

This article was written with AI assistance and reviewed for technical accuracy.
Part of the **Zero-Cost Cloud & DevOps* series — Follow for more free tutorials*

#aBotWroteThis