bitrise.yml

format_version: 4
default_step_lib_source: https://github.com/bitrise-io/bitrise-steplib.git

app:
  envs:
  # If you want to share this step into a StepLib
  - BITRISE_STEP_ID: genymotion-cloud-saas-start
  - BITRISE_STEP_VERSION: "0.1.7"
  - BITRISE_STEP_GIT_CLONE_URL: https://github.com/genymobile/bitrise-step-genymotion-cloud-saas-start.git
  - MY_STEPLIB_REPO_FORK_GIT_URL: git@github.com:Genymobile/bitrise-steplib.git
  # Define these in your .bitrise.secrets.yml
  - GMCLOUD_SAAS_EMAIL: $GMCLOUD_SAAS_EMAIL
  - GMCLOUD_SAAS_PASSWORD: $GMCLOUD_SAAS_PASSWORD
  - GMCLOUD_SAAS_API_TOKEN: $GMCLOUD_SAAS_API_TOKEN

workflows:
  ci:
    steps:
    - go-list:
    - golint:
    - errcheck:
    - go-test:

  run-all-tests:
    before_run:
    - test-credentials
    - test-api-token
    - test-adb-serial-port
    - test-several-devices
    - test-several-devices-with-adb-serial-port

  test-credentials:
    title: "Test Credentials"
    description: "This step tests that the user can login and start a device with credentials."
    steps:
    - change-workdir:
        title: Switch working dir to test / _tmp dir
        description: |-
          To prevent step testing issues, like referencing relative
          files with just './some-file' in the step's code, which would
          work for testing the step from this directory directly
          but would break if the step is included in another `bitrise.yml`.
        run_if: true
        inputs:
        - path: ./_tmp
        - is_create_path: true
    - path::./:
        title: Genymotion Cloud SaaS Start
        run_if: "true"
        inputs:
        - email: $GMCLOUD_SAAS_EMAIL
        - password:  $GMCLOUD_SAAS_PASSWORD
        - recipe_uuid:
    - script:
        inputs:
        - content: |
            #!/bin/bash
            echo "The value of 'GMCLOUD_SAAS_INSTANCE_UUID' is: $GMCLOUD_SAAS_INSTANCE_UUID
            echo "The value of 'GMCLOUD_SAAS_INSTANCE_ADB_SERIAL_PORT' is: $GMCLOUD_SAAS_INSTANCE_ADB_SERIAL_PORT
    - git::https://github.com/Genymobile/bitrise-step-genymotion-cloud-saas-stop.git:
          title: "Genymotion Cloud SaaS Stop"
          description: |-
           Stop Genymotion Cloud SaaS Android Devices.
          inputs:
          - instance_uuid: $GMCLOUD_SAAS_INSTANCE_UUID

  test-api-token:
    title: "Test API Token"
    description: "This step tests that the user can login and start a device with the API token."
    steps:
    - change-workdir:
        title: Switch working dir to test / _tmp dir
        description: |-
          To prevent step testing issues, like referencing relative
          files with just './some-file' in the step's code, which would
          work for testing the step from this directory directly
          but would break if the step is included in another `bitrise.yml`.
        run_if: true
        inputs:
        - path: ./_tmp
        - is_create_path: true
    - path::./:
        title: Genymotion Cloud SaaS Start
        run_if: "true"
        inputs:
        - api_token: $GMCLOUD_SAAS_API_TOKEN
        - recipe_uuid: 
        - adb_serial_port:
    - script:
        inputs:
        - content: |
            #!/bin/bash
            gmsaas --version
            echo "The value of 'GMCLOUD_SAAS_INSTANCE_UUID' is: $GMCLOUD_SAAS_INSTANCE_UUID
            echo "The value of 'GMCLOUD_SAAS_INSTANCE_ADB_SERIAL_PORT' is: $GMCLOUD_SAAS_INSTANCE_ADB_SERIAL_PORT
    - git::https://github.com/Genymobile/bitrise-step-genymotion-cloud-saas-stop.git:
          title: "Genymotion Cloud SaaS Stop"
          description: |-
           Stop Genymotion Cloud SaaS Android Devices.
          inputs:
          - instance_uuid: $GMCLOUD_SAAS_INSTANCE_UUID

  test-adb-serial-port:
    title: "Test ADB Serial Port"
    description: "This step tests the connection to the specified ADB port for Genymotion devices."
    steps:
    - change-workdir:
        title: Switch working dir to test / _tmp dir
        description: |-
          To prevent step testing issues, like referencing relative
          files with just './some-file' in the step's code, which would
          work for testing the step from this directory directly
          but would break if the step is included in another `bitrise.yml`.
        run_if: true
        inputs:
        - path: ./_tmp
        - is_create_path: true
    - path::./:
        title: Genymotion Cloud SaaS Start
        run_if: "true"
        inputs:
        - email: $GMCLOUD_SAAS_EMAIL
        - password: $GMCLOUD_SAAS_PASSWORD
        - recipe_uuid:
        - adb_serial_port:
    - script:
        inputs:
        - content: |
            #!/bin/bash
            echo "The value of 'GMCLOUD_SAAS_INSTANCE_UUID' is: $GMCLOUD_SAAS_INSTANCE_UUID
            echo "The value of 'GMCLOUD_SAAS_INSTANCE_ADB_SERIAL_PORT' is: $GMCLOUD_SAAS_INSTANCE_ADB_SERIAL_PORT
    - git::https://github.com/Genymobile/bitrise-step-genymotion-cloud-saas-stop.git:
          title: "Genymotion Cloud SaaS Stop"
          description: |-
           Stop Genymotion Cloud SaaS Android Devices.
          inputs:
          - instance_uuid: $GMCLOUD_SAAS_INSTANCE_UUID
    
  test-several-devices:
    title: "Test Several Devices"
    description: "This step tests that the user can login and start several devices with credentials."
    steps:
    - change-workdir:
        title: Switch working dir to test / _tmp dir
        description: |-
          To prevent step testing issues, like referencing relative
          files with just './some-file' in the step's code, which would
          work for testing the step from this directory directly
          but would break if the step is included in another `bitrise.yml`.
        run_if: true
        inputs:
        - path: ./_tmp
        - is_create_path: true
    - path::./:
        title: Genymotion Cloud SaaS Start
        run_if: "true"
        inputs:
        - email: $GMCLOUD_SAAS_EMAIL
        - password: $GMCLOUD_SAAS_PASSWORD
        - recipe_uuid: 
        - adb_serial_port: 
    - script:
        inputs:
        - content: |
            #!/bin/bash
            echo "The value of 'GMCLOUD_SAAS_INSTANCE_UUID' is: $GMCLOUD_SAAS_INSTANCE_UUID
            echo "The value of 'GMCLOUD_SAAS_INSTANCE_ADB_SERIAL_PORT' is: $GMCLOUD_SAAS_INSTANCE_ADB_SERIAL_PORT
    - git::https://github.com/Genymobile/bitrise-step-genymotion-cloud-saas-stop.git:
          title: "Genymotion Cloud SaaS Stop"
          description: |-
           Stop Genymotion Cloud SaaS Android Devices.
          inputs:
          - instance_uuid: $GMCLOUD_SAAS_INSTANCE_UUID
    
  test-several-devices-with-adb-serial-port:
    title: "Test Several Devices with ADB Serial Port"
    description: "This step tests that the user can login and start several devices with specific ADB serial port."
    steps:
    - change-workdir:
        title: Switch working dir to test / _tmp dir
        description: |-
          To prevent step testing issues, like referencing relative
          files with just './some-file' in the step's code, which would
          work for testing the step from this directory directly
          but would break if the step is included in another `bitrise.yml`.
        run_if: true
        inputs:
        - path: ./_tmp
        - is_create_path: true
    - path::./:
        title: Genymotion Cloud SaaS Start
        run_if: "true"
        inputs:
        - email: $GMCLOUD_SAAS_EMAIL
        - password: $GMCLOUD_SAAS_PASSWORD
        - recipe_uuid:
        - adb_serial_port:
    - script:
        inputs:
        - content: |
            #!/bin/bash
            echo "The value of 'GMCLOUD_SAAS_INSTANCE_UUID' is: $GMCLOUD_SAAS_INSTANCE_UUID
            echo "The value of 'GMCLOUD_SAAS_INSTANCE_ADB_SERIAL_PORT' is: $GMCLOUD_SAAS_INSTANCE_ADB_SERIAL_PORT
    - git::https://github.com/Genymobile/bitrise-step-genymotion-cloud-saas-stop.git:
          title: "Genymotion Cloud SaaS Stop"
          description: |-
           Stop Genymotion Cloud SaaS Android Devices.
          inputs:
          - instance_uuid: $GMCLOUD_SAAS_INSTANCE_UUID


  # ----------------------------------------------------------------
  # --- workflows to Share this step into a Step Library
  audit-this-step:
    steps:
    - script:
        inputs:
        - content: |-
            #!/bin/bash
            set -ex
            stepman audit --step-yml ./step.yml

  # ----------------------------------------------------------------
  # --- Utility workflows
  dep-update:
    title: Dep update
    description: |
      Used for updating bitrise dependencies with dep
    steps:
    - script:
        title: Dependency update
        inputs:
        - content: |-
            #!/bin/bash
            set -ex
            go get -u -v github.com/golang/dep/cmd/dep
            dep ensure -v
            dep ensure -v -update

  share-this-step:
    envs:
      # if you want to share this step into a StepLib
      - MY_STEPLIB_REPO_FORK_GIT_URL: $MY_STEPLIB_REPO_FORK_GIT_URL
      - BITRISE_STEP_ID: $BITRISE_STEP_ID
      - BITRISE_STEP_VERSION: $BITRISE_STEP_VERSION
      - BITRISE_STEP_GIT_CLONE_URL: $BITRISE_STEP_GIT_CLONE_URL
    description: |-
      If this is the first time you try to share a Step you should
      first call: $ bitrise share

      This will print you a guide, and information about how Step sharing
      works. Please read it at least once!

      As noted in the Step sharing guide you'll have to fork the
      StepLib you want to share this step into. Once you're done with forking
      the repository you should set your own fork's git clone URL
      in the `.bitrise.secrets.yml` file, or here in the `envs` section,
      as the value of the `MY_STEPLIB_REPO_FORK_GIT_URL` environment.

      You're now ready to share this Step, just make sure that
      the `BITRISE_STEP_ID` and `BITRISE_STEP_VERSION`
      environments are set to the desired values!

      To share this Step into a StepLib you can just run: $ bitrise run share-this-step

      Once it finishes the only thing left is to actually create a Pull Request,
      the way described in the guide printed at the end of the process.
    before_run:
    - audit-this-step
    steps:
    - script:
        inputs:
        - content: |-
            #!/bin/bash
            set -ex
            bitrise share start -c "${MY_STEPLIB_REPO_FORK_GIT_URL}"
            bitrise share create --stepid "${BITRISE_STEP_ID}" --tag "${BITRISE_STEP_VERSION}" --git "${BITRISE_STEP_GIT_CLONE_URL}"
            bitrise share finish