We will be creating a freestyle Jenkins project using docker. Before that, lets first understand what CICD and Build jobs.

What is CI/CD?

• CI or Continuous Integration is the practice of automating the integration of code changes from multiple developers into a single codebase. It is a software development practice where the developers commit their work frequently into the central code repository (Github or Stash). Then there are automated tools that build the newly committed code and do a code review, etc as required upon integration. The key goals of Continuous Integration are to find and address bugs quicker, make the process of integrating code across a team of developers easier, improve software quality and reduce the time it takes to release new feature updates.

• CD or Continuous Delivery is carried out after Continuous Integration to make sure that we can release new changes to our customers quickly in an error-free way. This includes running integration and regression tests in the staging area (similar to the production environment) so that the final release is not broken in production. It ensures to automate the release process so that we have a release-ready product at all times and we can deploy our application at any point in time.

What Is a Build Job?

A Jenkins build job contains the configuration for automating a specific task or step in the application building process. These tasks include gathering dependencies, compiling, archiving, or transforming code, and testing and deploying code in different environments.

Jenkins supports several types of build jobs, such as freestyle projects, pipelines, multi-configuration projects, folders, multibranch pipelines, and organization folders.

What is Freestyle Projects ?? 🤔

A freestyle project in Jenkins is a type of project that allows you to build, test, and deploy software using a variety of different options and configurations. Here are a few tasks that you could complete when working with a freestyle project in Jenkins:

Task-01

1. Create a new Jenkins freestyle project for your app.

   

2. Add Description

1. Source Code management; use GitHub Code URL

1. Always make sure to select the branch correctly; You mention the same branch in the Jenkins used in GitHub

1. Now let's begin Build Steps, Select Execute Shell and add commands as specified below.

Make sure that Docker is installed in your instance; if not install it by referring :kshitijaa.hashnode.dev/docker-for-devops-en..

After that add pipeline code as below

echo "Start My Build"
echo "Build the code and create docker image"
docker build -t node-todo:latest .
echo "Create Container for Node JS Code"
docker run -d -p 8000-8000 node-todo:latest

In the "Build" section of the project, add a build step to run the "docker build" command to build the image for the container.

Add a second step to run the "docker run" command to start a container using the image created.

1. Build Now

To access the app from outside allow port 8000 to the security group in the inbound rule of your instance.

This is the application.

Task-02

Create Jenkins project to run "docker-compose up -d" command to start the multiple containers defined in the compose file

Follow Steps 1 to 4 from Task-01. Make sure that your repo has docker-compose.yaml file in it. OR you can create docker-compose.yaml on referring like below.

version: '3'
services:
  app:
    image: node:latest
    container_name: app_main
    restart: always
    command: sh -c "yarn install && yarn start"
    ports:
      - 8000:8000
    working_dir: /app
    volumes:
      - ./:/app
    environment:
      MYSQL_HOST: localhost
      MYSQL_USER: root
      MYSQL_PASSWORD: 
      MYSQL_DB: test
  mongo:
    image: mongo
    container_name: app_mongo
    restart: always
    ports:
      - 27017:27017
    volumes:
      - ~/mongo:/data/db
volumes:
  mongodb:

• 

  

• Set up a cleanup step in the Jenkins project to run "docker-compose down" command to stop and remove the containers defined in the compose file.