From b72aa8602bf1ba8e1cadb3ecdda8f246ede08049 Mon Sep 17 00:00:00 2001
From: Baro1905 <93444313+Baro1905@users.noreply.github.com>
Date: Mon, 10 Jan 2022 09:18:43 +0300
Subject: [PATCH] Add .circleci/config.yml
---
.circleci/config.yml | 47 ++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 47 insertions(+)
create mode 100644 .circleci/config.yml
diff --git a/.circleci/config.yml b/.circleci/config.yml
new file mode 100644
index 0000000..7dc7f85
--- /dev/null
+++ b/.circleci/config.yml
@@ -0,0 +1,47 @@
+# Use the latest 2.1 version of CircleCI pipeline process engine.
+# See: https://circleci.com/docs/2.0/configuration-reference
+version: 2.1
+
+# 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.
+# See: https://circleci.com/docs/2.0/orb-intro/
+orbs:
+ # The python orb contains a set of prepackaged CircleCI configuration you can use repeatedly in your configuration files
+ # Orb commands and jobs help you with common scripting around a language/tool
+ # so you dont have to copy and paste it everywhere.
+ # See the orb documentation here: https://circleci.com/developer/orbs/orb/circleci/python
+ python: circleci/python@1.2
+
+# Define a job to be invoked later in a workflow.
+# See: https://circleci.com/docs/2.0/configuration-reference/#jobs
+jobs:
+ build-and-test: # This is the name of the job, feel free to change it to better match what you're trying to do!
+ # These next lines defines a Docker executors: https://circleci.com/docs/2.0/executor-types/
+ # You can specify an image from Dockerhub or use one of the convenience images from CircleCI's Developer Hub
+ # A list of available CircleCI Docker convenience images are available here: https://circleci.com/developer/images/image/cimg/python
+ # The executor is the environment in which the steps below will be executed - below will use a python 3.8 container
+ # Change the version below to your required version of python
+ docker:
+ - image: cimg/python:3.8
+ # Checkout the code as the first step. This is a dedicated CircleCI step.
+ # The python orb's install-packages step will install the dependencies from a Pipfile via Pipenv by default.
+ # Here we're making sure we use just use the system-wide pip. By default it uses the project root's requirements.txt.
+ # Then run your tests!
+ # CircleCI will report the results back to your VCS provider.
+ steps:
+ - checkout
+ - python/install-packages:
+ pkg-manager: pip
+ # app-dir: ~/project/package-directory/ # If you're requirements.txt isn't in the root directory.
+ # 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.
+ - run:
+ name: Run tests
+ # This assumes pytest is installed via the install-package step above
+ command: pytest
+
+# Invoke jobs via workflows
+# See: https://circleci.com/docs/2.0/configuration-reference/#workflows
+workflows:
+ sample: # This is the name of the workflow, feel free to change it to better match your workflow.
+ # Inside the workflow, you define the jobs you want to run.
+ jobs:
+ - build-and-test
pFad - Phonifier reborn
Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.
Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.
Alternative Proxies:
Alternative Proxy
pFad Proxy
pFad v3 Proxy
pFad v4 Proxy