diff --git a/.circleci/config.yml b/.circleci/config.yml deleted file mode 100644 index a114f291b316270979b12f1585d73cacfafc5b5e..0000000000000000000000000000000000000000 --- a/.circleci/config.yml +++ /dev/null @@ -1,41 +0,0 @@ -version: 2.1 - -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 - -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. - # For more details on extending your workflow, see the configuration docs: https://circleci.com/docs/2.0/configuration-reference/#workflows - jobs: - - build-and-test - - -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.9 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: requirements.txt # if you have a different name for your requirements file, maybe one that combines your runtime and test requirements. - - run: - name: Install the software and test it - # This assumes pytest is installed via the install-package step above - command: DEBUG=1 python setup.py install && rm -rf minijson && pytest diff --git a/.travis.yml b/.travis.yml new file mode 100644 index 0000000000000000000000000000000000000000..870418f30f0c5d41330706c8cdfe31d5026039fa --- /dev/null +++ b/.travis.yml @@ -0,0 +1,31 @@ +language: python +stages: + - name: test + - name: deploy + if: tag is present + +cache: pip +before_script: + - curl -L https://codeclimate.com/downloads/test-reporter/test-reporter-latest-linux-amd64 > ./cc-test-reporter + - chmod +x ./cc-test-reporter + - pwd + - ./cc-test-reporter before-build + - pip install -r requirements.txt + - pip install -U pytest-xdist pytest-cov pytest pytest-forked pluggy py mock + - python setup.py install +jobs: + include: + - stage: test + - stage: test + python: "3.8" + script: + - pytest -n 8 --cov=satella + after_script: + - coverage xml + - ./cc-test-reporter after-build -t coverage.py --exit-code $TRAVIS_TEST_RESULT + - stage: test + python: "pypy3.5" + script: + - pytest -n 8 + +