CI/CD pipeline basics in Django - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Output of a basic GitLab CI pipeline job

Given this simple GitLab CI job configuration, what will be the output when the job runs successfully?

Django

test_job:
  script:
    - echo "Running Django tests"
    - python manage.py test

A Running Django tests\nSyntaxError: invalid syntax

B Running Django tests\nNo tests found.

C Error: python command not found

D Running Django tests\nCreating test database for alias 'default'...\nSystem check identified no issues (0 silenced).\n...\nOK

💡 Hint

Think about what the 'python manage.py test' command outputs when tests pass.

The job echoes a message and then runs Django tests. If tests pass, Django outputs creation of test database and 'OK' at the end.

🧠 Conceptual

intermediate

Purpose of a CI/CD pipeline stage

In a CI/CD pipeline for a Django project, what is the main purpose of the 'build' stage?

A To compile source code and prepare artifacts for deployment

B To deploy the application to the production server

C To run automated tests on the codebase

D To monitor application performance after deployment

💡 Hint

Think about what 'build' means in software pipelines.

The build stage compiles code and prepares deployable packages or artifacts before testing or deployment.

🔀 Workflow

advanced

Correct order of CI/CD pipeline stages

Arrange the following CI/CD pipeline stages in the correct order for a Django project deployment.

A 3,1,2,4

B 3,2,1,4

C 2,3,1,4

D 1,3,2,4

💡 Hint

Think about what must happen before testing and deployment.

First build artifacts, then run tests, deploy to staging for validation, then deploy to production.

❓ Troubleshoot

advanced

Troubleshooting a failing Django test job in CI

A CI job running 'python manage.py test' fails with the error: 'ModuleNotFoundError: No module named 'django''. What is the most likely cause?

A The test command syntax is incorrect

B The test database is not configured correctly

C Django is not installed in the CI environment before tests run

D The tests contain syntax errors

💡 Hint

Consider what causes 'ModuleNotFoundError' in Python.

This error means the Django package is missing, likely because dependencies were not installed in the CI environment.

✅ Best Practice

expert

Best practice for secret management in CI/CD pipelines

What is the best practice for handling sensitive information like database passwords in a CI/CD pipeline for a Django application?

A Store secrets in environment variables managed by the CI/CD platform and inject them at runtime

B Hardcode secrets in the Django settings file committed to the repository

C Send secrets via email to the deployment team before each deployment

D Include secrets in the Docker image used for deployment

💡 Hint

Think about security and automation in pipelines.

Storing secrets in environment variables managed securely by the CI/CD system avoids exposing them in code or images.

Practice

1. What is the main purpose of a CI/CD pipeline in a Django project?

easy

A. To automate testing and deployment for faster and safer code delivery

B. To manually review code changes before deployment

C. To write Django models automatically

D. To create database backups

Solution

1. Step 1: Understand CI/CD pipeline purpose

   A CI/CD pipeline automates the process of testing and deploying code changes to reduce errors and speed up delivery.

2. Step 2: Match purpose with options

   To automate testing and deployment for faster and safer code delivery correctly states automation of testing and deployment, which is the core of CI/CD pipelines.

3. Final Answer:

   To automate testing and deployment for faster and safer code delivery -> Option A

4. Quick Check:

   CI/CD automates testing and deployment = D [OK]

Hint: CI/CD means automating tests and deploys [OK]

Common Mistakes:

• Confusing CI/CD with manual code review
• Thinking CI/CD creates Django code automatically
• Assuming CI/CD is for backups

2. Which of the following is the correct syntax to define a job named test in a GitLab CI/CD pipeline YAML file?

easy

A. test:
script:
- python manage.py test

B. job test {
run: python manage.py test
}

C. - job: test
steps:
- script: python manage.py test

D. test => {
script: 'python manage.py test'
}

Solution

1. Step 1: Recall GitLab CI YAML job syntax

   GitLab CI jobs are defined as job_name: followed by script: list with commands.

2. Step 2: Compare options with correct YAML syntax

   test: script: - python manage.py test matches the correct YAML format for a job named test running the Django test command.

3. Final Answer:

   test:\n script:\n - python manage.py test -> Option A

4. Quick Check:

   GitLab CI job syntax uses job_name: and script: list = A [OK]

Hint: GitLab CI jobs use job_name: and script: list [OK]

Common Mistakes:

• Using curly braces or other languages syntax
• Missing the dash before script commands
• Confusing job syntax with other CI tools

3. Given this GitHub Actions workflow snippet for a Django project:

jobs:
  test:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v3
      - name: Set up Python
        uses: actions/setup-python@v4
        with:
          python-version: '3.12'
      - name: Install dependencies
        run: pip install -r requirements.txt
      - name: Run tests
        run: python manage.py test

What will happen when this workflow runs?

medium

A. The workflow will fail because Python version is not specified

B. The workflow will check out code, set Python 3.12, install dependencies, and run Django tests

C. The workflow will skip installing dependencies

D. The workflow will deploy the Django app automatically

Solution

1. Step 1: Analyze each step in the workflow

   The workflow checks out code, sets up Python 3.12, installs dependencies from requirements.txt, then runs Django tests.

2. Step 2: Confirm expected behavior

   All steps are valid and will run in order, so tests will execute after setup.

3. Final Answer:

   The workflow will check out code, set Python 3.12, install dependencies, and run Django tests -> Option B

4. Quick Check:

   Steps run in order: checkout, setup, install, test = A [OK]

Hint: Read steps top to bottom to predict workflow actions [OK]

Common Mistakes:

• Assuming Python version missing causes failure
• Thinking dependencies are skipped
• Confusing test run with deployment

4. You have this GitLab CI job snippet:

test:
  script:
    - python manage.py test
  only:
    - main
    - develop

But tests are not running on your feature branch pushes. What is the likely problem?

medium

A. The script command is incorrect

B. The pipeline YAML file is missing

C. The job is limited to run only on main and develop branches

D. The tests are skipped because of syntax error in Python code

Solution

1. Step 1: Understand the 'only' keyword in GitLab CI

   The 'only' keyword restricts job execution to specified branches, here main and develop only.

2. Step 2: Analyze why feature branches don't run tests

   Since feature branches are not listed, the job does not run on them.

3. Final Answer:

   The job is limited to run only on main and develop branches -> Option C

4. Quick Check:

   'only' limits branches = B [OK]

Hint: 'only' controls branches where job runs [OK]

Common Mistakes:

• Thinking script command is wrong without checking
• Assuming pipeline file is missing
• Blaming test code syntax without evidence

5. You want to create a CI/CD pipeline for your Django app that runs tests only if code changes affect models.py or views.py. Which GitLab CI configuration snippet correctly implements this?

hard

A. test:
script:
- python manage.py test
only:
refs:
- main
- develop

B. test:
script:
- python manage.py test
except:
changes:
- models.py
- views.py

C. test:
script:
- python manage.py test
when: manual

D. test:
script:
- python manage.py test
only:
changes:
- models.py
- views.py

Solution

1. Step 1: Understand 'only: changes' in GitLab CI

   This setting runs the job only if specified files change in the commit.

2. Step 2: Match requirement with options

   test: script: - python manage.py test only: changes: - models.py - views.py uses 'only: changes' with models.py and views.py, so tests run only if these files change.

3. Final Answer:

   test:\n script:\n - python manage.py test\n only:\n changes:\n - models.py\n - views.py -> Option D

4. Quick Check:

   'only: changes' triggers job on file changes = C [OK]

Hint: 'only: changes' runs job on specific file changes [OK]

Common Mistakes:

• Using 'except' instead of 'only' for changes
• Using branch refs instead of file changes
• Setting job to manual instead of automatic