CI/CD for ML pipelines in ML Python - Model Pipeline Trace

Model Pipeline - CI/CD for ML pipelines

This pipeline shows how Continuous Integration and Continuous Delivery (CI/CD) helps automate machine learning workflows. It ensures that data, code, and models are tested, trained, and deployed smoothly and reliably.

Data Flow - 6 Stages

1Data Collection

10000 rows x 10 columns→Gather raw data from sources→10000 rows x 10 columns

User activity logs with 10 features

↓

2Data Preprocessing

10000 rows x 10 columns→Clean data, handle missing values→10000 rows x 9 columns

Removed one column with too many missing values

↓

3Feature Engineering

10000 rows x 9 columns→Create new features and scale data→10000 rows x 12 columns

Added 3 new features from existing ones

↓

4Model Training

8000 rows x 12 columns→Train model on training set→Trained model object

Random Forest classifier trained on 8000 samples

↓

5Model Validation

2000 rows x 12 columns→Evaluate model on validation set→Validation metrics (accuracy, loss)

Accuracy: 0.85, Loss: 0.35

↓

6Model Deployment

Trained model object→Deploy model to production environment→Model API endpoint

REST API ready to serve predictions

Training Trace - Epoch by Epoch

Epoch 1: 0.65 #######
Epoch 2: 0.50 #####
Epoch 3: 0.40 ####
Epoch 4: 0.35 ###
Epoch 5: 0.33 ##

Epoch	Loss ↓	Accuracy ↑	Observation
1	0.65	0.60	Model starts learning with moderate accuracy
2	0.50	0.72	Loss decreases and accuracy improves
3	0.40	0.80	Model converges with better performance
4	0.35	0.85	Training stabilizes with high accuracy
5	0.33	0.87	Slight improvement, model ready for validation

Prediction Trace - 4 Layers

Layer 1: Input Data

Layer 2: Feature Scaling

Layer 3: Model Prediction

Layer 4: Output Decision

Model Quiz - 3 Questions

What happens to the data shape after feature engineering?

A It increases in columns

B It decreases in rows

C It stays the same

D It becomes a model object

Key Insight

CI/CD pipelines automate the steps from data collection to model deployment, ensuring smooth updates and reliable machine learning models in production.

Practice

1. What is the main purpose of a CI/CD pipeline in machine learning projects?

easy

A. To manually update model parameters

B. To automate model training, testing, and deployment

C. To store large datasets only

D. To write machine learning algorithms from scratch

Solution

1. Step 1: Understand CI/CD pipeline role

   CI/CD pipelines automate repetitive tasks like training, testing, and deploying ML models.

2. Step 2: Compare options

   Only To automate model training, testing, and deployment describes automation of these tasks; others describe unrelated activities.

3. Final Answer:

   To automate model training, testing, and deployment -> Option B

4. Quick Check:

   CI/CD automates ML workflows = B [OK]

Hint: CI/CD means automating ML workflow steps [OK]

Common Mistakes:

• Thinking CI/CD is only for code storage
• Confusing manual updates with automation
• Assuming CI/CD writes ML algorithms

2. Which of the following is the correct YAML syntax snippet to trigger a CI/CD pipeline on every code push in GitHub Actions?

easy

A. on: [push]

B. trigger: push

C. when: code_push

D. event: commit

Solution

1. Step 1: Identify GitHub Actions trigger syntax

   GitHub Actions uses 'on:' keyword with event names like 'push' to trigger workflows.

2. Step 2: Validate options

   Only 'on: [push]' is valid YAML syntax for triggering on code push.

3. Final Answer:

   on: [push] -> Option A

4. Quick Check:

   GitHub Actions trigger = on: [push] [OK]

Hint: GitHub Actions uses 'on:' for triggers [OK]

Common Mistakes:

• Using 'trigger' instead of 'on'
• Wrong keywords like 'when' or 'event'
• Incorrect YAML list syntax

3. Given this simplified ML pipeline step in a CI/CD YAML file:

steps:
  - name: Train model
    run: python train.py --epochs 5
  - name: Test model
    run: python test.py
  - name: Deploy model
    run: python deploy.py

What will happen if train.py fails during execution?

medium

A. The pipeline stops and does not run test or deploy steps

B. The pipeline continues to test and deploy steps regardless

C. Only the deploy step is skipped, test runs

D. The pipeline retries the train step automatically

Solution

1. Step 1: Understand default CI/CD step behavior

   By default, if a step fails, the pipeline stops and next steps do not run.

2. Step 2: Apply to given steps

   If 'train.py' fails, 'test.py' and 'deploy.py' steps will not execute.

3. Final Answer:

   The pipeline stops and does not run test or deploy steps -> Option A

4. Quick Check:

   Step failure stops pipeline = A [OK]

Hint: Failed step stops pipeline unless configured otherwise [OK]

Common Mistakes:

• Assuming pipeline continues after failure
• Thinking only deploy step is skipped
• Believing automatic retries happen by default

4. You wrote this GitHub Actions step to deploy your ML model:

- name: Deploy model
  run: python deploy.py
  if: success()

But the deploy step runs even if the test step fails. What is the likely cause?

medium

A. The deploy.py script always succeeds regardless of tests

B. The 'if' condition should be 'if: failure()' to run on failure

C. GitHub Actions ignores 'if' conditions on run steps

D. The 'if: success()' condition is incorrectly indented

Solution

1. Step 1: Check YAML indentation rules

   In GitHub Actions, 'if:' must be at the same level as 'run:' to apply correctly.

2. Step 2: Analyze given snippet

   'if: success()' is indented under 'run:', so it is ignored and deploy runs always.

3. Final Answer:

   The 'if: success()' condition is incorrectly indented -> Option D

4. Quick Check:

   YAML indentation affects condition execution = D [OK]

Hint: Check YAML indentation for 'if:' conditions [OK]

Common Mistakes:

• Misplacing 'if:' under 'run:'
• Confusing success() with failure()
• Assuming scripts control step execution

5. You want to automate retraining your ML model weekly and also on every code push. Which CI/CD configuration best achieves this?

hard

A. trigger: push\nschedule: weekly\ncron: '0 0 * * 0'

B. on: push\nschedule: 'weekly' # invalid syntax

C. on: [push, schedule]\nschedule:\n - cron: '0 0 * * 0' # every Sunday midnight

D. on: [push]\nschedule: every Sunday

Solution

1. Step 1: Understand GitHub Actions triggers

   To trigger on code push and schedule, use 'on:' with both 'push' and 'schedule' keys.

2. Step 2: Validate cron syntax

   on: [push, schedule]\nschedule:\n - cron: '0 0 * * 0' # every Sunday midnight uses correct cron format for weekly schedule and valid YAML syntax.

3. Final Answer:

   on: [push, schedule]\nschedule:\n - cron: '0 0 * * 0' # every Sunday midnight -> Option C

4. Quick Check:

   Use 'on:' with push and schedule + valid cron [OK]

Hint: Use 'on:' with push and schedule plus cron for weekly [OK]

Common Mistakes:

• Using invalid schedule syntax
• Misplacing cron outside schedule
• Using unsupported keywords like 'trigger'