AndroidAPS/.circleci/config.yml

# 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.
orbs:
  android: circleci/android@1.0.3
  codecov: codecov/codecov@1.2.0

jobs:
  # Below is the definition of your job to build and test your app, you can rename and customize it as you want.
  build-and-test:
    # These next lines define the Android machine image executor: https://circleci.com/docs/2.0/executor-types/
    executor:
      name: android/android-machine

    steps:
      # Checkout the code as the first step.
      - checkout

      # The next step will run the unit tests
      - android/run-tests:
          test-command: ./gradlew testFullDebugUnitTest

      - android/run-tests:
          test-command: ./gradlew allDebugCoverage

      # Then start the emulator and run the Instrumentation tests!
      #      - android/start-emulator-and-run-tests:
      #          test-command: ./gradlew connectedDebugAndroidTest
      #          system-image: system-images;android-25;google_apis;x86

      # And finally run the release build
      #      - run:
      #          name: Assemble release build
      #          command: |
      #            ./gradlew assembleRelease
      - codecov/upload:
          file: './build/reports/jacoco/allDebugCoverage/allDebugCoverage.xml'

workflows:
  # Below is the definition of your workflow.
  # Inside the workflow, you provide the jobs you want to run, e.g this workflow runs the build-and-test job above.
  # CircleCI will run this workflow on every commit.
  # For more details on extending your workflow, see the configuration docs: https://circleci.com/docs/2.0/configuration-reference/#workflows
  dotests:
    jobs:
      - build-and-test