|
| 1 | +# Use the latest 2.1 version of CircleCI pipeline process engine. |
| 2 | +# See: https://circleci.com/docs/2.0/configuration-reference |
| 3 | +version: 2.1 |
| 4 | + |
| 5 | +# Orbs are reusable packages of CircleCI configuration that you may share across projects, enabling you to create encapsulated, parameterized commands, jobs, and executors that can be used across multiple projects. |
| 6 | +# See: https://circleci.com/docs/2.0/orb-intro/ |
| 7 | +orbs: |
| 8 | + # The python orb contains a set of prepackaged CircleCI configuration you can use repeatedly in your configuration files |
| 9 | + # Orb commands and jobs help you with common scripting around a language/tool |
| 10 | + # so you dont have to copy and paste it everywhere. |
| 11 | + # See the orb documentation here: https://circleci.com/developer/orbs/orb/circleci/python |
| 12 | + python: circleci/python@1.5.0 |
| 13 | + |
| 14 | +# Define a job to be invoked later in a workflow. |
| 15 | +# See: https://circleci.com/docs/2.0/configuration-reference/#jobs |
| 16 | +jobs: |
| 17 | + build-and-test: # This is the name of the job, feel free to change it to better match what you're trying to do! |
| 18 | + # These next lines defines a Docker executors: https://circleci.com/docs/2.0/executor-types/ |
| 19 | + # You can specify an image from Dockerhub or use one of the convenience images from CircleCI's Developer Hub |
| 20 | + # A list of available CircleCI Docker convenience images are available here: https://circleci.com/developer/images/image/cimg/python |
| 21 | + # The executor is the environment in which the steps below will be executed - below will use a python 3.10.2 container |
| 22 | + # Change the version below to your required version of python |
| 23 | + docker: |
| 24 | + - image: cimg/python:3.10.2 |
| 25 | + # Checkout the code as the first step. This is a dedicated CircleCI step. |
| 26 | + # The python orb's install-packages step will install the dependencies from a Pipfile via Pipenv by default. |
| 27 | + # Here we're making sure we use just use the system-wide pip. By default it uses the project root's requirements.txt. |
| 28 | + # Then run your tests! |
| 29 | + # CircleCI will report the results back to your VCS provider. |
| 30 | + steps: |
| 31 | + - checkout |
| 32 | + - python/install-packages: |
| 33 | + pkg-manager: pip |
| 34 | + # app-dir: ~/project/package-directory/ # If you're requirements.txt isn't in the root directory. |
| 35 | + # pip-dependency-file: test-requirements.txt # if you have a different name for your requirements file, maybe one that combines your runtime and test requirements. |
| 36 | + - run: |
| 37 | + name: Run tests |
| 38 | + # This assumes pytest is installed via the install-package step above |
| 39 | + command: pytest |
| 40 | + |
| 41 | +# Invoke jobs via workflows |
| 42 | +# See: https://circleci.com/docs/2.0/configuration-reference/#workflows |
| 43 | +workflows: |
| 44 | + sample: # This is the name of the workflow, feel free to change it to better match your workflow. |
| 45 | + # Inside the workflow, you define the jobs you want to run. |
| 46 | + jobs: |
| 47 | + - build-and-test |
0 commit comments