Menu

How CI/CD Changes the Way Developers Ship Software
πŸ“°

How CI/CD Changes the Way Developers Ship Software

DEV Community: cicdΒ·Soumyajit MukherjeeΒ·about 21 hours ago
#xkpbjRj3
#devtocicd#devto#dev#continuous#deployment
Reading 0:00
15s threshold

Imagine manually doing this every time you release an application:

Pull code Install dependencies Run tests Build application Copy files Configure server Restart application

Enter fullscreen mode

Exit fullscreen mode

It works.

But it's repetitive and error-prone.

CI/CD automates much of this process.

Continuous Integration

Continuous Integration means frequently integrating code changes and automatically validating them.

A pipeline might run:

git push ↓ Install dependencies ↓ Lint ↓ Run tests ↓ Build

Enter fullscreen mode

Exit fullscreen mode

If a test fails, the team gets immediate feedback.

Continuous Delivery

Continuous Delivery focuses on keeping software ready to deploy.

The pipeline may produce a deployment-ready artifact whenever code passes validation.

Continuous Deployment

Continuous Deployment goes further.

A successful pipeline can automatically deploy changes to production.

git push ↓ Tests ↓ Build ↓ Deploy ↓ Production

Enter fullscreen mode

Exit fullscreen mode

Why CI/CD…

Continue reading β€” create a free account

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