CI/CD pipeline for Flask - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define the Flask app instance.

Flask

from flask import Flask
app = Flask([1])

Drag options to blanks, or click blank then click option'

A"__name__"

B"app"

C"__main__"

D"flask"

Attempts:

3 left

💡 Hint

Common Mistakes

Using a string like 'app' instead of __name__ causes Flask to not find resources correctly.

The Flask app instance is created by passing __name__ to the Flask constructor. This helps Flask know where to look for resources.

2fill in blank

medium

Complete the GitHub Actions workflow trigger to run on push to the main branch.

Flask

on:
  push:
    branches:
      - [1]

Drag options to blanks, or click blank then click option'

Arelease

Bdevelop

Cfeature

Dmain

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'develop' or feature branches triggers workflows too often or on the wrong branch.

The workflow should trigger on pushes to the main branch, which is the default production branch in many projects.

3fill in blank

hard

Fix the error in the Dockerfile command to install dependencies from requirements.txt.

Flask

RUN pip install [1] requirements.txt

Drag options to blanks, or click blank then click option'

A--require

B-R

C-r

D--install

Attempts:

3 left

💡 Hint

Common Mistakes

Using uppercase or incorrect options causes pip to fail installing dependencies.

The correct pip option to install packages from a requirements file is -r.

4fill in blank

hard

Fill all three blanks to create a GitHub Actions job step that runs tests using pytest.

Flask

- name: Run tests
  run: [1] [2] [3]

Drag options to blanks, or click blank then click option'

Apytest

Bpython

C-m

Dtest

Attempts:

3 left

💡 Hint

Common Mistakes

Running 'pytest' directly may fail if not installed globally or in PATH.

To run pytest as a module, use python -m pytest. This ensures pytest runs in the Python environment.

5fill in blank

hard

Fill all three blanks to define a Dockerfile entrypoint that runs the Flask app.

Flask

ENTRYPOINT ["[1]", "-m", "[2]", "[3]"]

Drag options to blanks, or click blank then click option'

Apython

Bflask

Capp

Drun

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'app' instead of 'flask' or missing the 'run' command causes the container to not start the server.

The entrypoint runs python -m flask run to start the Flask development server inside the container.