CI/CD pipeline basics in Spring Boot - 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

Spring Boot

git add .
git commit -m "Add feature"
./mvnw clean package
./mvnw test
kubectl apply -f deployment.yaml

This sequence adds changes, commits code, builds the Spring Boot app, runs tests, and deploys to Kubernetes.

Execution Table

Step	Action	Command	Result	Next Step
1	Commit code	git commit -m "Add feature"	Code saved in repo	Build Stage
2	Build app	./mvnw clean package	Jar file created	Test Stage
3	Run tests	./mvnw test	All tests passed	Deploy Stage
4	Deploy app	kubectl apply -f deployment.yaml	App running in production	End
5	End	-	Pipeline complete	-

💡 Pipeline ends after successful deployment to production.

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4
Code State	Local changes	Committed	Built	Tested	Deployed
Build Artifact	None	None	Jar created	Jar created	Jar deployed
Test Status	Not run	Not run	Not run	Passed	Passed
Deployment Status	Not deployed	Not deployed	Not deployed	Not deployed	Running

Key Moments - 3 Insights

Why do we build the code before testing?

Building creates the executable file needed for tests; see execution_table step 2 and 3 where build produces the jar, then tests run on it.

What happens if tests fail?

The pipeline stops before deployment; in the table, if step 3 tests fail, step 4 deploy won't run.

Why deploy only after tests pass?

To ensure only working code reaches production, as shown by the flow from step 3 to 4 in execution_table.

Visual Quiz - 3 Questions

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

A Jar file created

B Code saved in repo

C All tests passed

D App running in production

💡 Hint

Check the 'Result' column for step 2 in the execution_table.

At which step does the pipeline deploy the app?

A Step 1

B Step 4

C Step 3

D Step 5

💡 Hint

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

If tests fail at step 3, what happens next?

A Pipeline continues to deploy

B Build stage repeats

C Pipeline stops before deployment

D Code is committed again

💡 Hint

Refer to key_moments about test failure stopping the pipeline.

Concept Snapshot

CI/CD pipeline basics:
1. Commit code to start pipeline.
2. Build compiles code into executable.
3. Test verifies code correctness.
4. Deploy moves app to production.
Pipeline stops if tests fail to keep production safe.

Full Transcript

A CI/CD pipeline automates software delivery. It starts when code is committed. Then the build stage compiles the code into a runnable file. Next, tests run to check for errors. If tests pass, the app is deployed to production. If tests fail, deployment stops to avoid errors in production. This flow ensures fast and safe delivery of software updates.