CI/CD pipeline basics in Node.js - Step-by-Step Execution

Concept Flow - CI/CD pipeline basics

Code Commit

↓

Build Stage

↓

Test Stage

↓

Deploy Stage

↓

Production Environment

The CI/CD pipeline starts with code commit, then builds the code, runs tests, and finally deploys to production.

Execution Sample

Node.js

git add .
git commit -m "Update"
npm run build
npm test
kubectl apply -f deployment.yaml

This sequence adds changes, commits code, builds the project, runs tests, and deploys to production.

Execution Table

Step	Action	Command	Result	Next Step
1	Code Commit	git add . && git commit -m "Update"	Code saved in repository	Build Stage
2	Build	npm run build	Project compiled successfully	Test Stage
3	Test	npm test	All tests passed	Deploy Stage
4	Deploy	kubectl apply -f deployment.yaml	Application deployed to production	Pipeline Complete
5	End	-	Pipeline finished successfully	-

💡 Pipeline stops after successful deployment to production.

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	Final
Code State	Local changes	Committed to repo	Built artifacts ready	Tests passed	Deployed to prod	Stable production

Key Moments - 3 Insights

Why do we run tests after building the code?

Tests run after build to check if the compiled code works correctly, as shown in step 3 of the execution table.

What happens if tests fail?

If tests fail, deployment does not happen. The pipeline stops after the test stage, preventing bad code from reaching production.

Why is deployment the last step?

Deployment is last to ensure only tested and built code reaches production, as seen in step 4 where deployment happens after successful tests.

Visual Quiz - 3 Questions

Look at the execution table, what is the result after the build step?

A All tests passed

B Project compiled successfully

C Code saved in repository

D Application deployed to production

💡 Hint

Check the 'Result' column in row 2 of the execution table.

At which step does the pipeline deploy the application?

A Step 4

B Step 2

C Step 3

D Step 5

💡 Hint

Look at the 'Action' column to find when deployment happens.

If tests fail, what happens to the deployment step?

A Build runs again

B Deployment proceeds anyway

C Deployment is skipped

D Code is committed again

💡 Hint

Refer to the key moments section about test failures stopping the pipeline.

Concept Snapshot

CI/CD pipeline automates code delivery.
Steps: Commit code -> Build -> Test -> Deploy.
Build compiles code.
Tests verify correctness.
Deploy sends code to production only if tests pass.

Full Transcript

A CI/CD pipeline automates software delivery by running steps in order: code commit, build, test, and deploy. When a developer commits code, the pipeline builds the project to compile the code. Then it runs tests to check if the code works correctly. If tests pass, the pipeline deploys the application to production. If tests fail, deployment stops to avoid errors in production. This process helps deliver reliable software quickly and safely.