CI/CD for ML pipelines in ML Python - Cheat Sheet & Quick Revision

Recall & Review

beginner

What does CI/CD stand for in the context of ML pipelines?

CI/CD stands for Continuous Integration and Continuous Delivery (or Deployment). It means automatically testing and delivering machine learning models and code changes.

beginner

Why is Continuous Integration important for ML pipelines?

Continuous Integration helps catch errors early by automatically testing code and model changes whenever someone updates the project. This keeps the ML pipeline stable and reliable.

intermediate

Name one key difference between CI/CD for traditional software and ML pipelines.

ML pipelines include extra steps like data validation, model training, and model evaluation, which are not common in traditional software CI/CD.

beginner

What is a common tool used for automating CI/CD in ML pipelines?

Tools like Jenkins, GitHub Actions, or specialized ML platforms like MLflow and Kubeflow Pipelines are used to automate CI/CD for ML.

beginner

How does Continuous Delivery benefit ML model deployment?

Continuous Delivery ensures that ML models are automatically prepared and ready to be deployed anytime, making updates faster and reducing manual errors.

What is the first step in a typical CI/CD pipeline for ML?

A Data validation and preprocessing

B Model deployment to production

C User feedback collection

D Monitoring model performance

The pipeline usually starts with validating and preparing data before training or testing models.

Which of these is NOT typically part of ML CI/CD pipelines?

A Code linting

B Data labeling by humans

C Model training

D Model evaluation

Data labeling is usually a manual or separate process, not part of automated CI/CD pipelines.

What does Continuous Deployment mean in ML pipelines?

A Automatically deploying models to production after passing tests

B Collecting data continuously

C Manually approving model updates

D Automatically training models daily

Continuous Deployment means models are automatically sent to production once they pass all checks.

Which tool can help automate ML pipeline workflows?

A Excel

B Photoshop

C Kubeflow Pipelines

D Slack

Kubeflow Pipelines is designed to automate ML workflows and CI/CD.

Why is testing important in ML CI/CD?

A To decorate the code

B To avoid using data

C To slow down deployment

D To check if the model code and data work well together

Testing ensures that code changes and data updates do not break the ML pipeline.

Explain the main stages of a CI/CD pipeline for machine learning projects.

Think about the steps from data to deploying a model automatically.

Describe how Continuous Integration helps maintain quality in ML pipelines.

Focus on how CI catches problems early.

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'