Menu

1 / 2

30-Day Cloud & DevOps Challenge: Day 8 — Jenkins: my First CI/CD Pipeline

DEV Community·Michelle·7 months ago
#2IKFuHfj
#issue#creating#jenkins#docker#pipeline
Reading 0:00
15s threshold

Yesterday, I had all three containers running with Docker Compose; frontend, backend, and PostgreSQL.

But there was still one manual step: every time I changed code, I had to rebuild and restart containers manually.

Today, I fixed that forever.

I installed Jenkins — an automation server that watches my GitHub repository and runs tasks automatically when code changes. This is the heart of CI/CD (Continuous Integration/Continuous Deployment).

First: What is Jenkins?

In one sentence: Jenkins is a tool that automatically runs tasks when your code changes.

The Problem Jenkins Solves

Without Jenkins (where I was):

Write code

git push

Manually run docker-compose up --build

Wait

Repeat for every change

With Jenkins:

Write code

git push

Jenkins AUTOMATICALLY builds and deploys

Done!

Analogy

Without Jenkins With Jenkins

You bake bread from scratch every morning Bread machine bakes automatically when you add ingredients

Manual, repetitive, error-prone Automatic, consistent, reliable

Step 1:…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.