DEV Community

Cover image for DevOps project: 🚀 Jenkins CI/CD Pipeline with Docker & Node.js
Ritesh Singh
Ritesh Singh

Posted on

DevOps project: 🚀 Jenkins CI/CD Pipeline with Docker & Node.js

#jenkins #cicd #docker #aws

🚀 Jenkins CI/CD Pipeline with Docker & Node.js

This project demonstrates a Jenkins CI/CD pipeline running on AWS EC2, which builds and deploys a simple Node.js app inside a Docker container, and pushes the image to Docker Hub.

📌 Features

  • Node.js sample app (Hello from Jenkins CI/CD + Docker + Node.js!)
  • Jenkins pipeline using Jenkinsfile
  • Automated build & deployment with Docker
  • Push Docker images to Docker Hub
  • GitHub Webhook integration for auto builds

🛠️ Tech Stack

  • Node.js – Application
  • Docker – Containerization
  • Jenkins – CI/CD pipeline
  • AWS EC2 – Jenkins & Docker host
  • Docker Hub – Image registry
  • GitHub – Source code repository

First Setting Up Jenkins on an AWS EC2 Instance

This guide provides step-by-step instructions to launch an AWS EC2 instance, install Jenkins, and access the Jenkins server. Follow these steps to set up a Jenkins server using Amazon Linux 2 on a t2.micro instance.

Prerequisites

  • An AWS account with appropriate permissions.
  • Basic knowledge of SSH and terminal commands.
  • A web browser to access the Jenkins dashboard.

Step 1: Log in to an AWS Account

  1. Navigate to the AWS Management Console.
  2. Log in with your AWS credentials (username, password, and MFA if enabled).
  3. In the AWS Console, locate the EC2 service under the "Compute" section or use the search bar to find "EC2."
  4. Click EC2 to access the EC2 Dashboard.

Step 2: Navigate to EC2 Dashboard

  1. In the EC2 Dashboard, select Instances from the left-hand menu.
  2. Click Launch instances to start creating a new EC2 instance. 3.

Step 3: Launch Instance

  1. In the "Launch an instance" wizard, configure the following:
    • Name: Enter my_jenkins_server.
    • Number of instances: Set to 1.
    • Amazon Machine Image (AMI): Choose Amazon Linux 2 AMI (HVM), SSD Volume Type (select the latest version available in your region).
    • Architecture: Select 64-bit (x86).
  2. Proceed to configure instance details.

Step 4: Configure Instance

  1. Instance Type: Select t2.micro (Free Tier eligible, 1 vCPU, 1 GiB memory).
  2. Key Pair:
    • If you have an existing key pair, select it from the dropdown.
    • If not, click Create new key pair, name it (e.g., jenkins-key), choose RSA and .pem format, and download the key pair. Store it securely.
  3. Leave default settings for storage unless specific requirements exist.
  4. Proceed to configure network settings.

Step 5: Configure Network Security Groups

  1. In the Network settings section:
    • Choose Create security group or select an existing one.
    • Add the following inbound rules:
      • Type: HTTP, Protocol: TCP, Port Range: 8080, Source: Anywhere (0.0.0.0/0) for Jenkins web access.
      • Type: SSH, Protocol: TCP, Port Range: 22, Source: Your IP or Anywhere (0.0.0.0/0) for SSH access.
    • Security Note: Allowing all traffic (0.0.0.0/0) for all ports is insecure. For production, restrict SSH to your IP and limit other traffic.
  2. Ensure port 8080 (Jenkins) and port 22 (SSH) are open.

Step 6: Review and Launch Instance

  1. Review the configuration (instance type, AMI, key pair, security group).
  2. Click Launch instance to provision the instance.
  3. Note the instance ID from the confirmation message.

Step 7: Connect to EC2 Instance

  1. In the EC2 Dashboard, go to Instances and wait for the instance to reach the Running state (verify "Status Checks" pass).
  2. Select the instance (my_jenkins_server) and click Connect.

  1. In the Connect to instance window, select the SSH client tab.

  1. Use the provided SSH command, e.g.: 
   ssh -i "jenkins-key.pem" ec2-user@<Public_IP_or_DNS>
Enter fullscreen mode Exit fullscreen mode

  • Replace with the instance’s public IP or DNS (found in instance details).
  • Ensure the .pem file permissions are restricted:

Step 8: Install Jenkins

  1. Connect to the instance via SSH, then run:
  • Update 
sudo apt update -y
Enter fullscreen mode Exit fullscreen mode

  • Install Java (Jenkins needs Java) 
sudo apt install openjdk-17-jdk -y
Enter fullscreen mode Exit fullscreen mode

  • Add Jenkins repository 
curl -fsSL https://pkg.jenkins.io/debian/jenkins.io-2023.key | sudo tee \
  /usr/share/keyrings/jenkins-keyring.asc > /dev/null
echo deb [signed-by=/usr/share/keyrings/jenkins-keyring.asc] \
  https://pkg.jenkins.io/debian binary/ | sudo tee \
  /etc/apt/sources.list.d/jenkins.list > /dev/null

- Install Jenkins
sudo apt update -y
sudo apt install jenkins -y
Enter fullscreen mode Exit fullscreen mode

  • Start Jenkins 
sudo systemctl start jenkins
sudo systemctl enable jenkins
Enter fullscreen mode Exit fullscreen mode

👉 Jenkins runs on http://:8080

Step 9: Configure Jenkins

  1. Open browser → http://:8080

  1. Get initial password: 
sudo cat /var/lib/jenkins/secrets/initialAdminPassword
Enter fullscreen mode Exit fullscreen mode

  1. Paste password in Jenkins UI.

  2. Install suggested plugins.

  1. Create admin user.

  1. instance configuration

  1. jenkins is ready now

Step 5: Install Docker on EC2 

sudo apt install docker.io -y
Enter fullscreen mode Exit fullscreen mode

👉 Restart Jenkins so it can use Docker:

sudo usermod -aG docker jenkins
sudo systemctl enable docker
sudo systemctl start docker
sudo systemctl restart jenkins
Enter fullscreen mode Exit fullscreen mode

## Create a GitHub Repository
### Folder structure

Docker-Jenkins-app/
│-- app.js
│-- package.json
│-- Dockerfile
│-- Jenkinsfile
│-- README.md
Enter fullscreen mode Exit fullscreen mode

Configure Jenkins Pipeline

  • Push your Docker-Jenkins-app repo to GitHub.
  • In Jenkins UI:
    • New Item → Name: docker-pipeline-ec2 → Select Pipeline

  • In Pipeline → Select Pipeline script from SCM

Setup GitHub Webhook

  1. Go to your repo → Settings → Webhooks → Add webhook.

  1. Payload URL: 
http://<EC2-Public-IP>:8080/github-webhook/
Enter fullscreen mode Exit fullscreen mode
  1. Content type: application/json
  2. Event: Just the push event

  1. save

Add Docker Hub Credentials in Jenkins

Open Jenkins Dashboard → Manage Jenkins → Credentials.

Click System → Global credentials (unrestricted) → Add Credentials.

Select Kind = Username with password.

  • Username = Your Docker Hub username

    • Password = Your Docker Hub password or personal access token how to create docker hub tokens

  • ID = dockerhub-creds (you will use this ID in Jenkinsfile)

  • Description = Docker Hub Credentials

Test

  1. Commit & push a small change to your repo (e.g., update app.js message).
  2. GitHub → Sends webhook → Jenkins job auto-triggers.
  3. Jenkins builds Docker image + runs container on EC2 And push the image into the docker hub image

  1. Access app at: 
http://<EC2-Public-IP>:4000
Enter fullscreen mode Exit fullscreen mode
  1. ✅ Now you’ll have a fully automated CI/CD pipeline on EC2 with webhooks.

📢 Follow My Journey

github

linkdin

Top comments (0)