CI/CD pipeline basics in Django - Step-by-Step Execution

Concept Flow - CI/CD pipeline basics

Code Commit

↓

Trigger Pipeline

↓

Build Stage

↓

Test Stage

↓

Deploy Stage

↓

Production Environment

↓

Feedback & Monitoring

This flow shows how code changes trigger automated steps: build, test, deploy, and then monitoring in production.

Execution Sample

Django

steps:
  - name: Build
    run: python manage.py collectstatic --noinput
  - name: Test
    run: python manage.py test
  - name: Deploy
    run: echo "Deploying to server..."

This sample pipeline runs build, test, and deploy commands for a Django project.

Execution Table

Step	Action	Command Run	Result	Next Step
1	Build Stage	python manage.py collectstatic --noinput	Static files collected successfully	Proceed to Test Stage
2	Test Stage	python manage.py test	All tests passed	Proceed to Deploy Stage
3	Deploy Stage	echo "Deploying to server..."	Deployment simulated	Pipeline Complete
4	Pipeline End	-	-	No further steps

💡 Pipeline ends after deploy stage completes successfully

Variable Tracker

Variable	Start	After Build	After Test	After Deploy
pipeline_status	Not started	Build successful	Tests passed	Deployed

Key Moments - 2 Insights

Why does the pipeline stop if tests fail?

The pipeline only moves to deploy if tests pass, as shown in execution_table row 2 where 'All tests passed' is required to proceed.

What happens if static files are not collected properly?

If the build stage fails (row 1), the pipeline will not proceed to testing or deployment to avoid deploying broken code.

Visual Quiz - 3 Questions

Look at the execution table, what is the pipeline_status after the Test Stage?

A Tests passed

B Build successful

C Deployed

D Not started

💡 Hint

Check variable_tracker column 'After Test' for pipeline_status value.

At which step does the pipeline simulate deployment?

A Step 1

B Step 3

C Step 2

D Step 4

💡 Hint

Look at execution_table row with 'Deploy Stage' and the command run.

If tests fail, what happens to the pipeline?

A It continues to deploy

B It restarts build

C It stops before deploy

D It skips tests

💡 Hint

Refer to key_moments explanation about pipeline stopping on test failure.

Concept Snapshot

CI/CD pipeline automates code delivery:
1. Code commit triggers pipeline
2. Build stage prepares code (e.g., collect static files)
3. Test stage runs automated tests
4. Deploy stage releases code if tests pass
5. Pipeline stops if any stage fails
Automates safe, fast delivery of Django apps.

Full Transcript

A CI/CD pipeline for Django starts when code is committed. The pipeline runs a build step to collect static files, then runs tests to check code quality. If tests pass, it proceeds to deploy the app. If any step fails, the pipeline stops to prevent bad code from reaching production. This automation helps deliver updates quickly and safely.