step.yml

#
# A couple of useful guides & docs:
#
# - Main Bitrise CLI docs: https://github.com/bitrise-io/bitrise/tree/master/_docs
# - Step Development Guideline: https://github.com/bitrise-io/bitrise/blob/master/_docs/step-development-guideline.md
# - Bitrise.yml format spec: https://github.com/bitrise-io/bitrise/blob/master/_docs/bitrise-yml-format-spec.md
# - Bitrise docs: http://devcenter.bitrise.io/
# - Bitrise CLI guides: http://devcenter.bitrise.io/bitrise-cli/

title: |-
  Autify Upload
summary: |
  Upload a build file to Autify for Mobile.
description: |
  [Autify for Mobile](https://autify.com/mobile) is a test automation platform for your native app.
  This step allows you to upload your app built in the previous steps to Autify.

  You need to build your app first by `Android Build`, `Xcode build for simulator`, etc.
  and refer the target build path (*.apk or *.app) at `Build path to test` input.

website: https://github.com/autifyhq/bitrise-step-autify-upload
source_code_url: https://github.com/autifyhq/bitrise-step-autify-upload
support_url: https://github.com/autifyhq/bitrise-step-autify-upload/issues

# If this step should be available only for certain project types
# just uncomment this `project_type_tags` section and include all the
# project types supported by the step. If the step can be used for all
# project types then you can just remove this section.
# If no `project_type_tags` specified (or specified as an empty array)
# that means the step can be used for any project type.
# You can find more information about project type tags in the Step Development Guideline:
# https://github.com/bitrise-io/bitrise/blob/master/_docs/step-development-guideline.md
#
project_type_tags:
  - ios
  - android
  - react-native
  - cordova
  - ionic
  - flutter

# Type tags are used for categorizing steps, for easier step discovery in Step Libraries.
# You can find more information about type tags in the Step Development Guideline:
# https://github.com/bitrise-io/bitrise/blob/master/_docs/step-development-guideline.md
type_tags:
  - test

# These properties define whether a Step is run in a given Workflow or not.
# You can find more information about this in the documentation here:
# https://devcenter.bitrise.io/en/steps-and-workflows/developing-your-own-bitrise-step/developing-a-new-step.html#setting-conditions-for-running-the-step
#
# is_always_run: false
# is_skippable: false
# run_if: ""

# Use the `deps` property to declare dependencies that you can fetch from an OS dependency manager.
# You can find more information about this in the documentation here:
# https://devcenter.bitrise.io/en/steps-and-workflows/developing-your-own-bitrise-step/developing-a-new-step.html#submodules-and-step-dependencies
#
# deps:
#   brew:
#   - name: cmake
#   apt_get:
#   - name: cmake

toolkit:
  bash:
    entry_file: step.sh

inputs:
  - access_token:
    opts:
      title: Access token of Autify for Mobile
      summary: Personal Access Token of Autify for Mobile
      is_expand: true
      is_required: true
      is_sensitive: true
  - workspace_id:
    opts:
      title: Workspace ID to upload
      summary: Your workspace ID of Autify for Mobile to upload the build
      is_expand: true
      is_required: true
  - build_path:
    opts:
      title: Build path to upload
      summary: |-
        The file location of your build file i.e. /path/to/ios.app or /path/to/android.apk.
        Typically, it's `$BITRISE_APP_DIR_PATH` for `Xcode build for simulator` step or `$BITRISE_APK_PATH` for `Android build` step.
      is_expand: true
      is_required: true
  - autify_path: autify
    opts:
      title: A path to Autify CLI
      is_expand: true
  - autify_cli_installer_url: https://autify-cli-assets.s3.amazonaws.com/autify-cli/channels/stable/install-cicd.bash
    opts:
      title: Autify CLI installer URL
      is_expand: true

outputs:
  - AUTIFY_BUILD_ID:
    opts:
      title: "Uploaded build id on Autify for Mobile"
  - AUTIFY_UPLOAD_EXIT_CODE:
    opts:
      title: "Exit code of the step"