{"id":15866,"date":"2024-02-27T12:18:40","date_gmt":"2024-02-27T06:48:40","guid":{"rendered":"https:\/\/opstree.com\/blog\/\/?p=15866"},"modified":"2025-07-31T23:46:34","modified_gmt":"2025-07-31T18:16:34","slug":"ci-cd-with-github-actions-concepts","status":"publish","type":"post","link":"https:\/\/opstree.com\/blog\/2024\/02\/27\/ci-cd-with-github-actions-concepts\/","title":{"rendered":"CI\/CD with GitHub Actions – Concepts"},"content":{"rendered":"\r\n

Welcome to the first part of our blog on GitHub Actions!<\/p>\r\n\r\n\r\n\r\n

This blog will delve into fundamental concepts essential for understanding GitHub Actions. Get ready to embark on a journey through the basics, paving the way for the upcoming implementation part of our blog. Stay tuned for hands-on demonstrations and practical applications in the next blog. Let’s dive in!<\/p>\r\n

<\/p>\r\n\r\n\r\n\r\n

What is GitHub Actions?<\/strong><\/h2>\r\n\r\n\r\n\r\n

GitHub Actions<\/a> enables users to automate various GitHub events, such as cloning a repository, generating Docker images, and testing scripts. Developers use it to automate workflows across issues, pull requests, and more. This means that users can build, test, and deploy code written in different languages and running on different platforms, all using the same automation tool.<\/p>\r\n\r\n\r\n\r\n

How do GitHub Actions work?<\/strong><\/h2>\r\n\r\n\r\n\r\n\r\n\r\n

GitHub Actions uses YAML files to define workflows. These YAML files<\/a> are stored in a .github\/workflows directory in the user’s repository. Each workflow consists of one or more jobs, and each job consists of one or more steps.<\/p>\r\n\r\n\r\n\r\n

GitHub Actions provides a wide range of tools and features that make it easy for users to configure and manage their workflows. as i mentioned earlier in the first paragraph, GitHub Actions allows automation of your software development workflows.<\/p>\r\n\r\n\r\n\r\n

Why should you use Github Actions? <\/strong><\/h2>\r\n\r\n\r\n\r\n

There are several benefits to using GitHub Actions for automation.<\/p>\r\n\r\n\r\n\r\n

1. Simplified workflows: <\/strong>GitHub Actions simplifies the process of building, testing, and deploying code.<\/p>\r\n\r\n\r\n\r\n

2. Integration with GitHub: <\/strong>GitHub Actions is tightly integrated with GitHub, which means that users can trigger actions based on events that occur within their repositories.<\/p>\r\n\r\n\r\n\r\n

4. Supports a wide range of platforms and languages<\/strong>: GitHub Actions supports many platforms and languages, means users can use the same automation tool for different projects and languages.<\/p>\r\n\r\n\r\n\r\n

5. Secure and reliable: <\/strong>GitHub Actions also provides built-in security features, such as the ability to store secrets securely and to control access to workflows.<\/p>\r\n\r\n\r\n\r\n

6. Cost-effective: <\/strong>GitHub Actions is a cost-effective automation tool. Users can use it for free for public repositories, and there is a generous free tier for private repositories.<\/p>\r\n\r\n\r\n\r\n

7. Easy to get started: <\/strong>GitHub Actions is easy to get started with. Users can use the visual editor to create workflows.<\/p>\r\n\r\n\r\n\r\n

How to set up GitHub action in GitHub repository :<\/strong><\/h3>\r\n\r\n\r\n\r\n

Till now, I have explained how one can add Github Action to the GitHub repository. I have taken an example of my Github Repository<\/a> which already has some code pushed into the main branch. In the GitHub repository, one must create (.github\/workflows\/directory) and add a .yml file.<\/p>\r\n\r\n\r\n\r\n

There are two ways to create a .yml file. In this blog, I have explained (Through Web Application (Github) directly)<\/strong><\/p>\r\n\r\n\r\n\r\n

Mention all the steps to create a .yml file:-<\/p>\r\n\r\n\r\n\r\n

a. Go to repository<\/p>\r\n\r\n\r\n\r\n

b. Click on Add File > Create New File<\/p>\r\n\r\n\r\n\r\n

\"\"<\/figure>\r\n\r\n\r\n\r\n

 <\/p>\r\n\r\n\r\n\r\n

c. Enter .github\/workflows\/main.yml ( It has to be in the same sequence)<\/p>\r\n\r\n\r\n\r\n

\"\"<\/figure>\r\n\r\n\r\n\r\n

d. Now, you can add the code to the main.yml file and commit changes to your GitHub repository.<\/p>\r\n\r\n\r\n\r\n

name: My GitHub Action Workflow 
on: 
  push:
  pull request:
    branches: 
       - main
       - feature
       - stg
       - dev
  workflow dispatch:
     inputs:
      environment:
        type: environment
        description: Select the environment.
      Boolean:
        type: choice
        description: Make a choice.
        options:
         - prod<\/code><\/pre>\r\n\r\n\r\n\r\n
How to view GitHub action activity:<\/strong><\/h3>\r\n\r\n\r\n\r\n
Once the GitHub actions are configured and start running.<\/p>\r\n\r\n\r\n\r\n
    \r\n
  1. Go to your repository on Github.com<\/strong><\/a><\/li>\r\n\r\n\r\n\r\n
  2. Under the repository name, click on the Actions tab<\/li>\r\n<\/ol>\r\n\r\n\r\n\r\n
    \"\"<\/figure>\r\n\r\n\r\n\r\n
     <\/p>\r\n\r\n\r\n\r\n
    3. <\/strong>Select the workflow(My GitHub Action Workflow) you want to see from the left sidebar.<\/p>\r\n\r\n\r\n\r\n
    \"\"<\/figure>\r\n\r\n\r\n\r\n
    4. <\/strong>Under \u201cWorkflow \u201d click the name of the run you want to see.<\/p>\r\n\r\n\r\n\r\n
    \"\"<\/figure>\r\n\r\n\r\n\r\n
     <\/p>\r\n\r\n\r\n\r\n
    5. <\/strong>One can view the result of each step by clicking on the workflow.<\/p>\r\n\r\n\r\n\r\n
    \"\"<\/figure>\r\n\r\n\r\n\r\n
    \"\"<\/figure>\r\n\r\n\r\n\r\n
    Here are some components of GitHub Actions or key concepts of GitHub Actions<\/strong> that I used<\/strong>.<\/p>\r\n\r\n\r\n\r\n
    The relationship between these components is illustrated below:<\/strong><\/h3>\r\n\r\n\r\n\r\n
    Using the flow diagram of GitHub action, I’ll try to explain how GitHub action works.<\/p>\r\n\r\n\r\n\r\n
    \"\"<\/figure>\r\n\r\n\r\n\r\n
    In practice, workflows are more generalized than a CD pipeline<\/a>, but they are closely related:<\/p>\r\n\r\n\r\n\r\n
      \r\n
    1. Workflows = pipelines<\/li>\r\n\r\n\r\n\r\n
    2. Jobs = stages<\/li>\r\n\r\n\r\n\r\n
    3. Steps = the series of procedures that make up a stage<\/li>\r\n<\/ol>\r\n\r\n\r\n\r\n
      1. Name<\/strong><\/p>\r\n\r\n\r\n\r\n
      A name for your workflow to help you identify it.<\/p>\r\n\r\n\r\n\r\n
      name: My GitHub Action Workflow 
      <\/code><\/pre>\r\n\r\n\r\n\r\n
      2. Trigger<\/strong><\/p>\r\n\r\n\r\n\r\n
      Specifies when the workflow should be executed. This can be based on events, schedules, or manual triggers. Trigger on a push or pull request to the main or features branch.<\/p>\r\n\r\n\r\n\r\n
      on: 
        push:
        pull request:
          branches: 
             - main
             - feature
             - stg
             - dev<\/code><\/pre>\r\n\r\n\r\n\r\n
      3. Steps<\/strong><\/p>\r\n\r\n\r\n\r\n
      Specify the individual tasks or commands that should be executed within a job. Steps run sequentially, and you can use built-in or custom actions.<\/p>\r\n\r\n\r\n\r\n
          steps:
            - name: code checkout
              uses: actions\/checkout@v2.
            - name: Set up Java version
              uses: actions\/setup-java@v1.
              with:
                java-version: '11'<\/code><\/pre>\r\n\r\n\r\n\r\n
      4. Jobs<\/strong><\/p>\r\n\r\n\r\n\r\n
      A workflow must have at least 1 job and can consist of multiple jobs that work together sequentially or in parallel. Each job is a series of steps that runs under the same runner (virtual environment).<\/p>\r\n\r\n\r\n\r\n
      jobs:
        build:
          runs-on: ubuntu-latest.
          steps:
            - name: code checkout
              uses: actions\/checkout@v2.
            - name: Set up Java version
              uses: actions\/setup-java@v1.
              with:
                java-version: '11'
            - name: Build with Maven
              run: mvn clean install.
            - name: Static Code Analysis with checkstyle
              run: mvn checkstyle:checkstyle<\/code><\/pre>\r\n\r\n\r\n\r\n
      5. Secrets<\/strong><\/p>\r\n\r\n\r\n\r\n
      You can access secrets (encrypted environment variables) in your workflow, typically used for sensitive information like API keys or passwords.<\/p>\r\n\r\n\r\n\r\n
          steps:
            - name: Install rsync 
              run: Sudo apt-get install rsync -y
            - name: Deploy to Server 1
              uses: easingthemes\/ssh-deploy@main
              env:
                SSH_PRIVATE_KEY: ${{secrets.EC2_SSH_KEY}}
                REMOTE_HOST: ${{ secrets.HOST_DNS }}
                REMOTE_USER: ${{ secrets.USERNAME }}
                TARGET: ${{ secrets.TARGET_DIR }}       
                aws-region: ${{ env.AWS_REGION }}
                ARGS: -r
                SCRIPT_BEFORE: |
                    whoami
                    ls -al <\/code><\/pre>\r\n\r\n\r\n\r\n
      6. Workflow<\/strong><\/p>\r\n\r\n\r\n\r\n
        \r\n
      1. The workflow is an automated procedure that you add to your repository.<\/li>\r\n\r\n\r\n\r\n
      2. They are made up of one or more jobs and can be scheduled or triggered by an event.<\/li>\r\n\r\n\r\n\r\n
      3. It can be used to build, test, package, release, or deploy a project on GitHub.<\/li>\r\n<\/ol>\r\n\r\n\r\n\r\n
        7. Runners<\/strong><\/p>\r\n\r\n\r\n\r\n
          \r\n
        1. A runner is a server that has the GitHub Action Runner application installed.<\/li>\r\n\r\n\r\n\r\n
        2. you can use a runner hosted by GitHub, or you can host your own.<\/li>\r\n<\/ol>\r\n\r\n\r\n\r\n
          GitHub Actions can use two types of runners: hosted and self-hosted. <\/strong><\/p>\r\n\r\n\r\n\r\n